chore(release): bump to v1.3.0#167
Merged
Merged
Conversation
Minor release reflecting the multi-Java runtime support and the release-pipeline hardening landed since v1.2.1. Source-of-truth bump: gradle.properties argusVersion 1.2.1 → 1.3.0. Mirror references updated: - install.sh, install.ps1: fallback + example version - charts/argus/Chart.yaml: version + appVersion - charts/argus/README.md, deploy/sdkman/README.md - docs/getting-started.md, docs/kubernetes.md, docs/usage.md - site/index.html: header badge + starter snippet - Formula/argus.rb: url + libexec install + desc CHANGELOG.md grows a 1.3.0 entry covering Java 11/17/21 multi-runtime support, per-subcommand --help, install-script SHA-256 verification, checksums.txt + native-image auto-trigger in release.yml, the starter ApplicationContextRunner integration tests, and the bug fixes (VM Name "<pid>:" leak, bad-PID exit code, Java 21 API leakage in agent/server/starter). Per the release-sync skill convention, Formula/argus.rb sha256 still references the v1.2.1 artifact and MUST be recomputed in a follow-up PR after release.yml uploads argus-cli-1.3.0-all.jar to the v1.3.0 GitHub Release. brew install will fail with a checksum mismatch until that follow-up is merged. Build verified: ./gradlew compileJava :argus-cli:test → exit 0. Signed-off-by: rlaope <piyrw9754@gmail.com>
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
Minor release reflecting the multi-Java runtime support and the release-pipeline hardening landed since v1.2.1.
gradle.propertiesargusVersion1.2.1 → 1.3.0. Mirror references updated across 11 files per the project's "version sync on release, never skip" rule. Validated by grepping the entire repo for1.2.1and finding only the intentional CHANGELOG history references that remain.CHANGELOG.mdgrows a 1.3.0 entry covering:--helpchecksums.txt+ native-image auto-trigger inrelease.ymlApplicationContextRunnerintegration testsKnown follow-up
Formula/argus.rbsha256still references the v1.2.1 artifact. After this PR is tagged v1.3.0 andrelease.ymluploadsargus-cli-1.3.0-all.jar, a separate small PR will recompute the hash.brew installwill fail with a checksum mismatch until that follow-up is merged — same well-understood pattern we used for v1.2.1 (#161).Test plan
grep -rn '1\\.2\\.1'returns no live references (only CHANGELOG history)./gradlew compileJava :argus-cli:test→ exit 0release.ymluploads JARs +checksums.txtdocker.ymlpublishes bothargus:1.3.0andargus-agent:1.3.0to GHCR (the docker.yml fix from fix(ci): build argus-agent JAR before docker push + teach release-sync to verify GHCR #159 is now well exercised)native-image.ymlauto-fires (the auto-trigger from chore: add CHANGELOG.md and complete the release pipeline #164 gets its first real test)