Repository navigation
chore: release v3.3.25 - #756
Merged
Merged
Conversation
Member
Author
|
@greptileai please review this generated version-only release PR. |
 |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
alongubkin
added a commit
that referenced
this pull request
Oct 5, 2026
…'s changelog (#876) ## What Two release-flow bugs that would hit the next stable release: 1. **The next version PR fails "Release qualification".** Prepare now bumps `infra/helm/alien-manager/Chart.yaml` and `infra/aws-ecs-manager/variables.tf`, but the detect step's file allowlist in `release-qualification.yml` doesn't list them, so it fails with "Release PR contains non-version files". 2. **Each GitHub release body lists the previous release's changes.** `generate-changelog` runs `git-cliff --latest` before the new tag exists, so it renders the range ending at the previous tag. The v3.3.26 body lists #707–#756, which shipped in v3.3.25. ## How 1. Add both files to the allowlist, and normalize their version fields (`version`/`appVersion` in the chart, the `alien-manager:v…` image default in the module) so any other change to them still fails the check. 2. Use `--unreleased --tag v<version>`: the commits since the last tag, rendered under the new version. ## Verification - On a scratch commit that applies prepare's own `sed` bumps for 3.3.27 to `main`: the old allowlist rejects exactly the two files; the new allowlist and the metadata check pass. A second scratch commit that also changes `type:` in the chart and the image registry in the module fails with "Release PR changes non-version metadata". - `git-cliff 2.14.2` with `cliff.toml` on `main`: `--latest` renders #753–#779 (the v3.3.26 range); `--unreleased --tag v3.3.27` renders #553–#873, the 68 commits since v3.3.26. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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.
Version-only release PR generated by the stable release workflow. The Release qualification check builds and records the exact artifact set. After every required check passes and this merges, run the stable publish action from
mainto promote those qualified artifacts.