Uh oh!
There was an error while loading. Please reload this page.
chore(master): release authup 0.2.0 - #1
Merged
tada5hi merged 1 commit intoAug 4, 2026
Conversation
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Free Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
github-actionsBotforce-pushed
the
release-please--branches--master--components--authup
branch
2 times, most recently
from
August 4, 2026 06:47
fa047d8 to
5d97c4fComparegithub-actionsBotforce-pushed
the
release-please--branches--master--components--authup
branch
from
August 4, 2026 07:29
5d97c4f to
a583622Comparegithub-actionsBotforce-pushed
the
release-please--branches--master--components--authup
branch
from
August 4, 2026 08:06
a583622 to
2cedd7bComparetada5hi added a commit
that referenced
this pull request
Aug 19, 2026
charts/authup sets skip-github-release because chart-releaser owns the authup-<version> release: cr upload --skip-existing skips an existing release wholesale rather than uploading into it, so a release-please release would leave the chart .tgz unattached and the index.yaml download URL dangling. With that the only package, release-please created zero releases, so it never reached the step that swaps a merged release PR's "autorelease: pending" label for "autorelease: tagged". PR #1 kept the label, and every run since aborted PR creation with "There are untagged, merged release PRs outstanding" while still exiting 0, leaving the workflow green while no release PR was ever opened again. Add a root package (release-type simple, component root) linked to the chart, the shape PrivateAIM/helm uses. It creates one real release per cycle, which restores the label swap and makes releases_created meaningful, and linked-versions keeps both components on one version. This replaces the label-clearing workflow step added in 93ecbba. bootstrap-sha moves to the authup-0.2.0 commit: root has no release yet, so it would otherwise inherit the whole history including refactor(authup)!, releasing root as 0.3.0 and dragging the chart along through linked-versions.
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 freeto 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 beepboop
0.2.0 (2026-08-04)
⚠ BREAKING CHANGES
Features
Bug Fixes
Code Refactoring
This PR was generated with Release Please. See documentation.