dbatools-buildref-index.json - Add ReleaseDate for SQL Server 2022 and 2025 CUs#10277
Open
andreasjordan wants to merge 1 commit intodevelopmentfrom
Open
dbatools-buildref-index.json - Add ReleaseDate for SQL Server 2022 and 2025 CUs#10277andreasjordan wants to merge 1 commit intodevelopmentfrom
andreasjordan wants to merge 1 commit intodevelopmentfrom
Conversation
…022 and 2025 CUs Dates sourced directly from Microsoft documentation: - https://learn.microsoft.com/en-us/troubleshoot/sql/releases/sqlserver-2022/build-versions - https://learn.microsoft.com/en-us/troubleshoot/sql/releases/sqlserver-2025/build-versions SQL Server 2022 (v16): RTM (2022-11-16) + CU1 through CU24 (2026-03-12) SQL Server 2025 (v17): CU1 (2026-01-29) through CU3 (2026-03-12) (do Test-DbaBuild) Co-authored-by: Andreas Jordan <andreasjordan@users.noreply.github.com>
Collaborator
Author
|
If it is that ease to add the dates based on the official sources, then we should to that. And we should let Claude check the current contents of the json to be sure it is correct. We should add the non-CU dates as well (add all we can get) and continue with all the currently supported versions. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
ReleaseDatefield to RTM and all named CU entries for SQL Server 2022 (v16, RTM+CU1–CU24) and SQL Server 2025 (v17, CU1–CU3).Dates sourced directly from official Microsoft documentation:
This enables time-based compliance checking as described in issue #9259, where organizations want to verify instances are within a time window (e.g., 6 months) rather than a fixed number of CUs behind.
Closes #9259
Generated with Claude Code