Repository navigation
chore(release): 0.11.0 - #32
Merged
Merged
Conversation
Cuts 0.11.0, the first published release since 0.9.1. 0.10.0 was merged and versioned but never tagged, so it never reached crates.io; 0.11.0 carries its changes together with the taskDigestMultibase work merged in #31. - Cargo.toml: 0.10.0 -> 0.11.0 - CHANGELOG.md: [Unreleased] moves under [0.11.0] - 2026-09-22, with an "Upgrading from 0.9" section for consumers crossing both releases at once; the [0.10.0] section is marked as never published - README.md: the upgrade-ordering table gains a 0.11.0 row and notes that 0.10.0 first ships in 0.11.0 No code changes. The affinidi-tdk 0.12 -> 0.16 bump (#30) is a dev-dependency only and is not user-visible. Signed-off-by: Glenn Gore <glenn.g@affinidi.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
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.
Cuts 0.11.0, the first release published to crates.io since 0.9.1.
Why 0.11.0 and not 0.10.0
Cargo.tomlhas said 0.10.0 since #28, and the CHANGELOG has a[0.10.0] - 2026-09-11section, but nov0.10.0tag was ever pushed, so 0.10.0 never reached crates.io (latest there is 0.9.1). Since then #31 (feat!,taskDigestMultibase) merged, and its code already carries#[deprecated(since = "0.11.0")]. So this releases both as 0.11.0 rather than retroactively tagging 0.10.0.Changes
Cargo.toml:0.10.0→0.11.0CHANGELOG.md:[Unreleased]content moves under## [0.11.0] - 2026-09-22, with[Unreleased]left emptyDTGCredentialErroris#[non_exhaustive](+9 variants),new_member_vmc/new_delegate_vdc/new_vwcdeprecated in favour ofnew_member_vmc_for/new_delegate_vdc_for/new_vwc_for_session, andDTGCommon::task_digest_multibasebreaks exhaustive struct literals. Ordering: verifiers first (from 0.10.0's stricter checks); 0.11.0 adds none.[0.10.0]section is marked never published to crates.ioREADME.md: the upgrade-ordering table gains a 0.11.0 row ("Any order") and notes that 0.10.0 first ships in 0.11.0No code changes. The file has no compare links, so none to update.
affinidi-tdk bump (#30)
Not user-visible:
affinidi-tdk(0.12 → 0.16) is a dev-dependency only (examples and integration tests), so no CHANGELOG entry. The affinidi crates that are in the public API (affinidi-data-integrity0.7:DataIntegrityProof,DataIntegrityErrorvia#[from];affinidi-secrets-resolver0.5:&Secretinsign) are unchanged since 0.9.1.Verification (local, on this commit)
cargo fmt --check: cleancargo clippy --all-targets -- -D warnings,--all-featuresand--no-default-features: cleancargo test --all-features: 186 passed, 0 failedcargo test --no-default-features: 170 passed, 0 failedcargo doc --no-deps, both feature sets: buildscargo publish --dry-run --locked: packaged 23 files (561.9 KiB, 140.0 KiB compressed), verify build OK, upload aborted (dry run)Pre-existing, not addressed here:
RUSTDOCFLAGS="-D warnings" cargo doc --no-default-featuresfails on intra-doc links toDTGCredential::sign/verify_proof_with_public_key, which only exist behindaffinidi-signing. docs.rs builds default features, and CI does not run rustdoc, so it does not block the release.Publishing (after merge — not done in this PR)
Earlier release tags (
v0.9.0,v0.9.1) are annotated, not signed, on the merge commit, with avX.Y.Z — <summary>message. To match:(Use
git tag -sinstead of-aif you want it signed; earlier tags were not.) The tag push triggers.github/workflows/publish.yml, which checks tag ==Cargo.tomlversion, skips if 0.11.0 is already on crates.io, then publishes via Trusted Publishing in thecrates-ioenvironment.