Repository navigation
ci: clean up build metadata naming - #106
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
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.
Summary
Cleans up CI artifact naming and build metadata presentation without changing the active Release Please integration contract.
CI artifacts
CI artifacts now use SemVer build metadata:
The GitHub Actions artifact container uses the same base name. Release artifacts remain unchanged as
HeadDB-<version>.jar.Build information
Build metadata presentation is simplified:
A rerun is shown as
64.2. Channels are normalized for display asCI,Release, andLocalrather than exposing lowercase machine values.Release workflow wording
Renames only our workflow-facing labels:
release_please→prepare_release_prPrepare release PRThe following implementation-sensitive Release Please details are deliberately unchanged:
<!-- x-release-please-version -->markersRELEASE_PLEASE_TOKENrelease-please-config.json.release-please-manifest.jsongoogleapis/release-please-actiondependencyNo manual repository settings or secret changes are required.