Skip to content

chore: release v0.15.0 - #560

Open
LKSNDRTMLKV wants to merge 1 commit into
mainfrom
chore/release-0-15-0
Open

LKSNDRTMLKV wants to merge 1 commit into
mainfrom
chore/release-0-15-0

Conversation

@LKSNDRTMLKV

Copy link
Copy Markdown
Member

Cuts 0.15.0 from main at cd8cd05d: the 100 commits since v0.14.0, on dpp-core 0.22.0. No code changes here.

What changes

  • The version, in the four places docs/governance/RELEASE.md names. Cargo.toml [workspace.package] and api/openapi.yaml info.version move to 0.15.0. Both OpenAPI bundles were regenerated, and the only line that moved in each is the version. In Cargo.lock, the 13 workspace members' version lines change and nothing else.
  • CHANGELOG.md. [Unreleased] becomes [0.15.0] - 2026-10-30, and an empty [Unreleased] heading stays above it. Two additions:

Release checklist

Item State
1. just check Green on this branch (see below)
2. Integration tests Not run locally. CI runs the Postgres and testcontainers tiers on this PR
3. CHANGELOG Cut, as above
4. Migrations 0041_retired_status, 0042_passport_identifier_index, 0043_personal_data_record, 0044_idempotency_claim_token, all in ops/pg/
5. Bootstrap flow Not run yet. It is a step before the tag, under a throwaway profile, because odal bootstrap overwrites the profile's key
6. README The crate map matches the 12 crates in crates/ plus cli/. The README no longer carries a dpp-core version table or a resolver route table, so neither can drift
7. Sections reconciled No removed route or renamed field is described outside Breaking. Two Added entries refuse requests 0.14.0 accepted: a write that stores a personal-data field without a personalData statement now gets 422, and a third concurrent import gets 429. They are left under Added for the reviewer to judge
8. cargo audit Part of just check
9. dpp-core pin The published 0.22.0, with no [patch]

just openapi-check passes, and so does spec-version-check: api/openapi.yaml and Cargo.toml agree on 0.15.0.

After this merges

  1. Wait for CI on the merge commit, including both Container image checks.
  2. Run the remaining checks before the tag:
    • migrate a v0.14.0 database that holds real passports through 0041–0044;
    • build release-candidate images locally and run them end to end;
    • run odal bootstrap under a throwaway profile;
    • run the nightly fuzz job on the merge commit.
  3. Tag v0.15.0. Pushing the tag publishes both images, and there is no dry run.

The CHANGELOG date is today. If the tag lands on a later day, the date moves with it.

@LKSNDRTMLKV LKSNDRTMLKV added this to the v0.15.0 milestone Oct 30, 2026
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