Skip to content

RouteContract v0.1.0-rc2

Pre-release
Pre-release

Choose a tag to compare

View all tags
@ym0506 ym0506 released this 21 Aug 02:12
· 4 commits to main since this release
Immutable release. Only release title and notes can be modified.
v0.1.0-rc2
4cb8b36
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

RouteContract v0.1.0-rc2 is an immutable prerelease candidate for exact-tag installation and external validation. It is not the final stable v0.1.0 release and does not establish adoption or production readiness.

What changed since RC1:

  • preserved the annotated RC1 tag and its failed evidence run without retagging or replacing assets;
  • fixed release-evidence collection for a digest-qualified MySQL image by binding the official repository namespace, exact registry digest, and one resolved image ID;
  • advanced project coordinates and the reviewed version-derived installation form to RC2 while retaining the RC1 form byte-for-byte;
  • refreshed the pinned Maven OSV database snapshot after the prior generation URL became unavailable.

Verified boundary:

  • Java 17, ShardingSphere-JDBC exactly 5.5.3;
  • normally returning, non-interrupted, synchronous non-batch PreparedStatement execution;
  • SQLExecutionHook-reported physical JDBC execution attempts and structural manifest changes only;
  • no claim of a complete route plan, physical-table count, transaction commit, business success, performance, security, or upstream endorsement.

Evidence:

  • tag commit: 4cb8b368fef4ca15ad2f09a8c4a17f820e80d16b
  • release-evidence run: https://github.com/ym0506/routecontract/actions/runs/32438464149
  • workflow artifact: routecontract-release-evidence-4cb8b368fef4ca15ad2f09a8c4a17f820e80d16b
  • public assets: eleven checksummed payloads plus SHA256SUMS
  • supply chain: 154 Maven packages; 3 reviewed test/example-graph findings; 0 unreviewed findings; 2 unresolved manual license reviews

unreviewed=0 does not mean zero vulnerabilities, and the automated license-policy result is not legal clearance. Current exception/review windows expire on 2026-08-27.

Install only from the attached checksummed assets and follow the exact RC2 instructions in the repository README. Independent recruitment is not active until a separate committed activation record passes the public validator.

Assets 15
Loading