docs(changelog): backfill 6.22.0 release commit short-SHA - #1052
Merged
Conversation
Appends `aa5ba5b` to the [6.22.0] heading, matching every other shipped version header. Lands after the post-release reset of develop to main — a backfill pushed before that sync is silently discarded, which is the order #1004 followed after 6.20.1. The tag pushed at release time never carries its own suffix; main acquires it one release later, when this commit rides the next release PR. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01D1wR59A8Z7d3QGYnm8q2KQ
Coverage Report for CI Build 33858350577Warning No base build found for commit Coverage: 89.925%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsRequires a base build to compare against. How to fix this → Coverage Stats
💛 - Coveralls |
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
3 participants
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.
Step 6 of the release flow: appends
— `aa5ba5b`to the## [6.22.0]heading, matching every other shipped version header.Lands after the post-release reset of
developtomain— a backfill pushed before that sync is silently discarded, which is the order #1004 followed after 6.20.1.developandmainare both ataa5ba5b3as of this branch.One line in
CHANGELOG.md. No code change.Release 6.22.0 — closed out
main:aa5ba5b3v6.22.0→ Release published withffcertificate-6.22.0.zip(3.6 MB)developreset tomainThe first tag push landed before #1051 merged, so it pointed at
aba5aec2(header still6.21.0) andrelease.yml's version sanity check failed — no Release, no zip. The tag was recreated onaa5ba5b3and the workflow passed. Worth noting only because the gate did exactly its job.🤖 Generated with Claude Code
https://claude.ai/code/session_01D1wR59A8Z7d3QGYnm8q2KQ
Generated by Claude Code