Skip to content

chore(release): 0.11.0 - #32

Merged
stormer78 merged 1 commit into
mainfrom
release/0.11.0
Sep 22, 2026
Merged

stormer78 merged 1 commit into
mainfrom
release/0.11.0

Conversation

@stormer78

Copy link
Copy Markdown
Contributor

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.toml has said 0.10.0 since #28, and the CHANGELOG has a [0.10.0] - 2026-09-11 section, but no v0.10.0 tag 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.0
  • CHANGELOG.md:
    • [Unreleased] content moves under ## [0.11.0] - 2026-09-22, with [Unreleased] left empty
    • a lead paragraph and an Upgrading from 0.9 section for consumers crossing 0.10.0 and 0.11.0 at once: DTGCredentialError is #[non_exhaustive] (+9 variants), new_member_vmc / new_delegate_vdc / new_vwc deprecated in favour of new_member_vmc_for / new_delegate_vdc_for / new_vwc_for_session, and DTGCommon::task_digest_multibase breaks exhaustive struct literals. Ordering: verifiers first (from 0.10.0's stricter checks); 0.11.0 adds none.
    • the [0.10.0] section is marked never published to crates.io
  • README.md: the upgrade-ordering table gains a 0.11.0 row ("Any order") and notes that 0.10.0 first ships in 0.11.0

No 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-integrity 0.7: DataIntegrityProof, DataIntegrityError via #[from]; affinidi-secrets-resolver 0.5: &Secret in sign) are unchanged since 0.9.1.

Verification (local, on this commit)

  • cargo fmt --check: clean
  • cargo clippy --all-targets -- -D warnings, --all-features and --no-default-features: clean
  • cargo test --all-features: 186 passed, 0 failed
  • cargo test --no-default-features: 170 passed, 0 failed
  • cargo doc --no-deps, both feature sets: builds
  • cargo 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-features fails on intra-doc links to DTGCredential::sign / verify_proof_with_public_key, which only exist behind affinidi-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 a vX.Y.Z — <summary> message. To match:

git fetch origin
MERGE_SHA=$(git rev-parse origin/main)   # confirm this is the squash-merge of this PR
git tag -a v0.11.0 "$MERGE_SHA" -m "v0.11.0 — taskDigestMultibase; first publish of 0.10.0's issue-time validation"
git push origin v0.11.0

(Use git tag -s instead of -a if you want it signed; earlier tags were not.) The tag push triggers .github/workflows/publish.yml, which checks tag == Cargo.toml version, skips if 0.11.0 is already on crates.io, then publishes via Trusted Publishing in the crates-io environment.

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>
@stormer78
stormer78 requested a review from a team as a code owner September 22, 2026 11:39
@stormer78
stormer78 merged commit 1d49eaf into main Sep 22, 2026
7 checks passed
@stormer78
stormer78 deleted the release/0.11.0 branch September 22, 2026 18:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant