Repository navigation
ci: bootstrap Release Please for BuildSystem artifacts - #35
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.
Release Please owns version bumps, release PRs, tags and GitHub releases. Bootstrap records the actual existing v4.0.0-grounds.16 release and its peeled commit; no next version is forced. Uses already accessible organization RELEASE_PLEASE_TOKEN so PR checks and release publication events trigger. Artifact workflow now responds only to release.published, checks out its exact tag and uploads the two JARs without creating releases, modifying release notes or overwriting existing assets. Preserves upstream Gradle/Sonatype and runtime/deployment behavior. Local checks: official config schema and both YAML files valid; baseline matches existing annotated tag, which is an ancestor of main; diff check clean. Full Java/Docker CI and independent review required before merge. First actual RP-generated release and artifact publication remain acceptance gates. No manual release/tag or cluster write.