Update confidential ledger changelog release date#38843
Open
Tewatia5355 wants to merge 1 commit into
Open
Conversation
Set the 1.1.2-beta.6 changelog heading to the release date and remove the skipped 1.1.2-beta.5 unreleased placeholder so release-mode changelog verification passes. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the @azure-rest/confidential-ledger changelog to satisfy release-mode changelog verification by dating the 1.1.2-beta.6 entry and removing the skipped 1.1.2-beta.5 unreleased placeholder.
Changes:
- Updated
1.1.2-beta.6heading from “Unreleased” to the release date2026-06-05. - Removed the unpublished
1.1.2-beta.5 (Unreleased)placeholder section.
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
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.
Packages impacted by this PR
@azure-rest/confidential-ledgerIssues associated with this PR
N/A
Describe the problem that is addressed by this PR
The release pipeline verifies the package changelog with
-ForRelease:$true. The current changelog still had unreleased entries for beta.6 and the skipped beta.5 placeholder, causing verification to fail.What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
The release entry needs a real date. This PR dates
1.1.2-beta.6and removes the skipped beta.5 placeholder instead of assigning a fake date to an unpublished version.Are there test cases added in this PR? (If not, why?)
No code changes. Verified with:
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
N/A
Checklists