chore: release main - #9
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
2 times, most recently
from
April 21, 2026 01:59
3712ebb to
18f3758
Compare
4 tasks
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
from
April 21, 2026 02:22
18f3758 to
854d5f7
Compare
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
release-please's default updater for Chart.yaml only bumps 'version:' and strips inline YAML comments (including the 'x-release-please-version' markers), leaving appVersion frozen at the previous release and deleting the markers the next release-please run needs to locate the lines. - Restore appVersion to 0.3.0 so the committed chart matches the release (CI's sed commands in .github/workflows/ci.yaml also stamp the same value at publish time, but the committed Chart.yaml is what helm install uses from the repo source). - Restore both 'x-release-please-version' markers and the explanatory comment block. - Pin the extra-files entry for Chart.yaml to the 'generic' updater so future release-please runs preserve the markers and update both 'version' and 'appVersion' in lockstep. Co-Authored-By: kyle_hunter@bcit.ca <kyle_hunter@bcit.ca>
Contributor
|
Took over to address both Devin Review findings on Root cause: release-please's default auto-detected updater for Fixes in 00c8741:
CI's |
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
3 tasks
kphunter
added a commit
that referenced
this pull request
Apr 21, 2026
) Follow-up to #12 / #9. Two related cleanups: 1. Remove the temporary graduation overrides that forced release-please to cut a clean '0.3.0' instead of '0.3.0-rc': - 'release-as': '0.3.0' - 'prerelease': false With '0.3.0' now on main, leaving these in would make release-please keep proposing 0.3.0 on every run (no-op but noisy) and block the next normal rc bump. 2. Remove the vestigial 'component': 'haproxy-operator' entry. Under strict-D this repo uses 'include-component-in-tag': false, so tags are 'vX.Y.Z' (no component prefix). The component field was a holdover from pre-strict-D (when the tag was 'haproxy-operator-v*'). With 'separate-pull-requests': false + no custom title pattern, release-please renders the release PR title as 'chore: release main' — which contains no ${component} token. On the post-merge run of PR #9 this caused release-please to log 'PR component: undefined does not match configured component: haproxy-operator' while building the release for path '.', and abort without creating the v0.3.0 tag or GitHub release. The follow-up 'dispatch-publish' step was therefore skipped, so the 0.3.0 image/chart were never published and the moving 'stable'/'latest' OCI pointers were not moved. Dropping the single-package component brings the config in line with a normal single-component strict-D repo (compare tech-ops-docs) and lets release-please parse 'chore: release main' correctly on future releases. Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Co-authored-by: kyle_hunter@bcit.ca <kyle_hunter@bcit.ca>
Author
|
🤖 Created releases: 🌻 |
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.
🤖 I have created a release beep boop
0.3.0
0.3.0 (2026-04-21)
Features
Bug Fixes
This PR was generated with Release Please. See documentation.