chore: release app 1.1.0 - #10
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
from
August 29, 2026 08:48
7a8c06f to
bbdb2cc
Compare
Contributor
Author
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
8 times, most recently
from
September 4, 2026 12:13
a8d7041 to
373406d
Compare
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
3 times, most recently
from
September 4, 2026 12:18
727cc29 to
1bd3f26
Compare
Vad1mo
added a commit
that referenced
this pull request
Sep 4, 2026
The docs, CLAUDE.md, CHECKLIST.md and the settings.yml comment all said a release pull request gets zero workflow runs because GITHUB_TOKEN raises no events. Measured on this repository: every run on a release pull request's head is created and held at action_required because github-actions[bot] pushed the branch. Approving the held DCO and Hygiene runs on #10 made both execute and pass. The consequence for required status checks stands, each release would need a manual approval, but the mechanism and the remedy's framing were wrong. Also rewords PATCHed in settings.yml, which a newer typos flags. Signed-off-by: Vadim Bauer <vb@container-registry.com>
Vad1mo
added a commit
that referenced
this pull request
Sep 4, 2026
…erialise release runs (#31) * ci: name the app release line, start adopted repositories at 0.1.0, serialise release runs The release pull requests did not match harbor-scanner-trivy's: the app line's title carried no line name next to the chart's, its header was pack-neutral prose and its footer an unlinked file name. Both lines now use the scanner's form: chore: release app X.Y.Z, a header that says what the merge publishes, and a linked docs/RELEASES.md, which bootstrap repoints at the adopted repository. initial-version: 0.1.0 on both lines. release-please starts at 1.0.0 when no tag exists and never consults the manifest's 0.0.0, so the template's first chart release and every adopted repository's first app release contradicted the docs. The open chart PR re-renders to 0.1.0. A concurrency group on release-please.yml. Two pushes to main two seconds apart ran it in parallel and each opened a chart release PR (#29, #30) on the same branch. Runs queue and are never cancelled. Signed-off-by: Vadim Bauer <vb@container-registry.com> * fix(bootstrap): keep the release header true without the Go pack With --lang=none the publish workflows are gone but the app release pull request still promised an image and binaries. Bootstrap now rewrites that clause to the tag and GitHub release, which is all the merge does. Signed-off-by: Vadim Bauer <vb@container-registry.com> * style: trim comments to the why Signed-off-by: Vadim Bauer <vb@container-registry.com> * ci: one release-please concurrency group for every ref A workflow_dispatch from a feature branch reconciles main with the same config and manifest but sat in its own group keyed on the ref, so the duplicate release pull request the group exists to prevent was one click away. The group is now a fixed string. The comment also said runs are never cancelled; GitHub keeps at most one pending run per group and a newer run replaces it, which is safe here because release-please reconciles from full history rather than consuming events. Signed-off-by: Vadim Bauer <vb@container-registry.com> * docs: the release pull request's runs wait for approval, they do exist The docs, CLAUDE.md, CHECKLIST.md and the settings.yml comment all said a release pull request gets zero workflow runs because GITHUB_TOKEN raises no events. Measured on this repository: every run on a release pull request's head is created and held at action_required because github-actions[bot] pushed the branch. Approving the held DCO and Hygiene runs on #10 made both execute and pass. The consequence for required status checks stands, each release would need a manual approval, but the mechanism and the remedy's framing were wrong. Also rewords PATCHed in settings.yml, which a newer typos flags. Signed-off-by: Vadim Bauer <vb@container-registry.com> --------- Signed-off-by: Vadim Bauer <vb@container-registry.com>
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
7 times, most recently
from
September 10, 2026 07:44
39b82e7 to
20bcf2b
Compare
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
from
September 10, 2026 11:41
20bcf2b to
7fbf664
Compare
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.
App release. Merging tags
vX.Y.Zand publishes the image and binaries.1.1.0 (2026-09-10)
Features
Bug Fixes
Squash-merge to release. See docs/RELEASES.md.