chore(release): bump version to 0.1.5 - #265
Merged
Merged
Conversation
v0.1.4 was tagged during the paused release attempt and its candidate predates the bug fixes that landed since (#250, #255, #261). Release tags are immutable, so the relaunched container release takes the next patch version. Regenerates SOFTWARE-LICENSE-NOTICES.html for the workspace crate version strings.
robinnsc
requested review from
LeeroyHannigan,
amrith,
c33howard,
jcshepherd,
pdf-amzn and
yesyayen
as code owners
August 13, 2026 22:05
LeeroyHannigan
approved these changes
Aug 13, 2026
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
2 participants
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.
What
Bumps the workspace version from
0.1.4to0.1.5(one line in the rootCargo.toml), refreshes the twelve workspace-member entries inCargo.lock,and regenerates
SOFTWARE-LICENSE-NOTICES.htmlfor the crate version strings.No dependency or source change.
Why
The
v0.1.4release attempt was paused before promotion so the fixes in#250, #255, and #261 could land — its candidate (
sha-c34aac11…) predatesthem all. The
v0.1.4tag is already public on the remote, and release tagsare immutable, so the relaunched container release takes the next patch
version. Same reasoning as #257, one version later.
After this merges, the relaunch is: tag
v0.1.5on the merged commit,dispatch
release-image, verify, mirror (ghcr-mirror+ manual ECR), sign,and promote via the new
promote-imageworkflow.Testing done
cargo check --workspace --all-targets --locked— clean on top of all fivefreshly merged PRs (fix(postgres): concurrent UpdateItem upserts creating one item must all succeed #250, fix: never print passwords in bootstrap conflict errors; unpin ca-cer… #255, fix: update table must merge attribute definitions #261, ci: two-person promotion of a verified candidate to version + latest #262, ci: mirror Cosign signature artifacts through the GHCR mirror job #264).
Cargo.lockdiff verified: only the twelveextenddb-*workspace cratesmoved
0.1.4→0.1.5; no third-party entries changed.SOFTWARE-LICENSE-NOTICES.htmldiff verified: onlyextenddb*versionstrings;
devtools/generate-software-license-notices --checkpasses.Checklist
cargo test --workspace) — not re-run: no source ordependency change; the merged code was tested by its own PRs' CI
cargo fmt --check) — not applicable, no Rust source changedcargo clippy -- -W clippy::pedantic) — not applicable, no Rust source changedStoragetrait, auth model, on-diskformat, or public CLI surface, an RFC has been accepted or is linked
below. Otherwise, an ADR captures the decision (link below).
ADR / RFC: n/a — version metadata only.
Breaking changes
None.
By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache License 2.0 and I agree to the Developer Certificate of
Origin (DCO). See CONTRIBUTING.md for details.