Repository navigation
Bump Beacon to v1.3.4 and enforce version bumps - #33
Merged
Merged
Conversation
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.
Beacon's startup fix in #32 merged with VERSION still at 1.3.0, even though published tags had reached v1.3.3. The shared release workflow could silently choose another patch tag without updating the file. Bump VERSION to 1.3.4 and require an explicit version for future changes.
just release-check, document the policy, and add AGENTS.md instructions requiring a version bump before opening or updating any PR.Validation: 32 checks against isolated Git histories passed, including missing bumps on unreleased bases, stale/colliding tags, malformed versions, and release retries.
just release-check, Bash syntax checks, actionlint v1.7.12, andgit diff --checkpassed. This PR changes versioning and workflows only.The existing main release already failed at the GoReleaser build step before this PR: https://github.com/open-ships/beacon/actions/runs/36778358810. This PR does not resolve that separate build failure.