chore(release): prepare 2.1.0#93
Merged
Merged
Conversation
- Versions: gradle.properties 2.0.1-SNAPSHOT -> 2.1.0-SNAPSHOT; browser SDK package.json 2.0.1-SNAPSHOT -> 2.1.0. - CHANGELOG: add the [2.1.0] entry (Added / Changed), and backfill the comparison link refs (incl. the [2.0.0] link the 2.0.0 cut omitted). - @SInCE: bump the 9 tags across the 4 files added after the v2.0.0 tag from @SInCE 2.0.1 to @SInCE 2.1.0 (CoseAlgorithm, CredentialAlgorithms, CeremonyConfig, AdminService). - Docs/site: sweep current-version references (CLAUDE.md, README, stability, SECURITY, RELEASE, site/index.html, site/og-image.svg) to 2.1.0; historical notes and the older changelog history are preserved. A backward-compatible minor release driven by the crypto-agility + post-quantum-readiness feature (ADR 0019): new CoseAlgorithm enum, configurable offered/accepted COSE algorithm lists on CeremonyConfig wired through all three adapters, and per-credential algorithm visibility. No public API removed; the HTTP /auth/** wire contract is unchanged. The minor bump (not 2.0.1) reflects the new public API. Note: site/og-image.png (the pre-rendered social card) still shows v2.0.0 and must be regenerated from the updated og-image.svg. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.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
Prepares the 2.1.0 release (a backward-compatible minor bump from the
2.0.1-SNAPSHOTdevelopment line). The release is dated 2026-06-23.The minor bump — rather than the
2.0.1the dev line was opened with — reflects that the crypto-agility work sincev2.0.0introduces new public API (CoseAlgorithm, configurableoffered/acceptedCOSE lists onCeremonyConfig,CredentialAlgorithms.coseAlgorithm,AdminService.listCredentialsByAlgorithm). No public API is removed and the HTTP/auth/**wire contract is unchanged.What changed in this PR
gradle.properties2.0.1-SNAPSHOT → 2.1.0-SNAPSHOT(the tag drives the published version perRELEASE.md); browser SDKpackage.json2.0.1-SNAPSHOT → 2.1.0.@sinceretags — the 9@since 2.0.1tags across the 4 files added afterv2.0.0bumped to@since 2.1.0(CoseAlgorithm,CredentialAlgorithms,CeremonyConfig,AdminService).[2.1.0] — 2026-06-23entry (Added / Changed), plus backfilled comparison link refs including the[2.0.0]link the 2.0.0 cut had omitted.CLAUDE.md,README.md,docs/stability.md,SECURITY.md,RELEASE.md,site/index.html, andsite/og-image.svg. Historical notes preserved.What's in 2.1.0 (since v2.0.0)
offeredAlgorithms/acceptedAlgorithms), backward-compatible defaults, per-credential algorithm visibility, and honest HS256-vs-ES256 JWT framing. No PQC algorithm is added (gated upstream by hardware/CTAP2/COSE/WebAuthn4J).check(opt-in viaPK_RUN_E2E=1) plus a dedicatede2ematrix job.In-progress browser-SDK ceremony work (RegistrationService, FakeAuthenticator, etc.) is unreleased and not surfaced in the changelog.
Notes / follow-ups
site/og-image.png(the pre-rendered social card) still shows v2.0.0 and must be regenerated from the updatedog-image.svg— a binary-asset step outside this PR../gradlew clean build test) runs in CI on the pushedv2.1.0tag.v2.1.0tag (RELEASE.md mode A), then publish the browser SDK to npm.🤖 Generated with Claude Code