feat(ci): switch release-please to Maven (java) flow with snapshots#132
Merged
Conversation
Mirror the Vulpes-Backend setup: use the `java` release-type so release-please manages the Maven SNAPSHOT lifecycle (release -> bump to next -SNAPSHOT) and drive the version in gradle.properties via the generic updater. Add the snapshot CI that flow implies, matching the release path: - `version` job reads gradle.properties on non-release pushes - `publish-snapshot` publishes to the snapshot Maven repo (java-client / velocity-plugin already route SNAPSHOT/BETA/ALPHA there) - `build-context-snapshot` + `docker-snapshot` build & push a snapshot image on every non-release push Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
Test results 6 files 6 suites 0s ⏱️ Results for commit 5191dc4. |
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.
Re-applies the Maven conversion that was part of #131 but did not make it onto
main(only the docker-split commit got merged). Cherry-picked cleanly onto currentmain(now at 1.14.1).Mirrors the Vulpes-Backend release pipeline.
Changes
release-please-config.json: package switched torelease-type: javaso release-please manages the Maven SNAPSHOT lifecycle (release → bump to next-SNAPSHOT);extra-filesuses the generic updater forgradle.properties.release-please.yml: add the snapshot CI matching the release path:versionjob readsgradle.propertieson non-release pushespublish-snapshot→ snapshot Maven repo (java-client/velocity-pluginalready route SNAPSHOT/BETA/ALPHA there)build-context-snapshot+docker-snapshotbuild & push a snapshot image on every non-release pushAfter merge
Expect release-please to open a
1.14.2-SNAPSHOTbump PR (the java strategy's release↔snapshot dance, same as Vulpes).gradle.propertiesis intentionally left at1.14.1— release-please drives it from here. Snapshot jobs stay skipped until the version is a-SNAPSHOT.No dependency on other PRs —
v2.3.0and the docker-split are already onmain.🤖 Generated with Claude Code