Skip to content

chore(release): v0.3.0 — GCP + Azure + AGPLv3 relicense#47

Merged
TechAlchemistX merged 2 commits intomainfrom
chore/v0.3.0-release
Apr 19, 2026
Merged

chore(release): v0.3.0 — GCP + Azure + AGPLv3 relicense#47
TechAlchemistX merged 2 commits intomainfrom
chore/v0.3.0-release

Conversation

@TechAlchemistX
Copy link
Copy Markdown
Owner

Summary

Release PR for v0.3.0. Bump workspace version 0.3.0-alpha.00.3.0 and stamp CHANGELOG [0.3.0] - 2026-04-19. Squash-merging this lands the version flip on main; I then tag v0.3.0 signed on the resulting commit to trigger the release workflow.

What ships as v0.3.0

  • 2 new backendssecretenv-backend-gcp (GCP Secret Manager) + secretenv-backend-azure (Azure Key Vault)
  • Canonical #key=value fragment grammar locked in (v0.2.1 internal)
  • Strict-mode mock test harness retrofitted across every backend (v0.2.2 → v0.2.7 internal)
  • Phase 0 groundwork — shared factory_helpers, Backend::check_extensive trait default, parallel check() via tokio::join!
  • Closing-audit fixes + items 18-20strict::Rule refactor, IndexMap in fragment_directives, Response::with_stdin_fragment chainable, Azure vault-URL regex fix, tightened drift-catch assertions, fragment-vocabulary doc links
  • Relicense MIT → AGPL-3.0-only + Contributor License Agreement (pre-launch breaking change; install base zero at flip time)

Last public release: v0.2.0 on 2026-04-18 (still on crates.io / Homebrew / GH Releases under MIT). The v0.2.1 → v0.2.7 internal patches were dev-merged without separate publishes per the aggregate-release posture.

Test plan

  • cargo fmt --check
  • cargo clippy --workspace --all-targets --all-features -- -D warnings
  • cargo test --workspace — 442/442
  • cargo deny check
  • cargo audit
  • Integration smoke — 250/250 across 7 live backends (local, aws-ssm, aws-secrets, 1password, vault, gcp, azure). Full report: kb/wiki/validation/2026-04-19-v0.3-phase2-azure-smoke.md.
  • CI green on this PR
  • Tag v0.3.0 signed + push → release workflow publishes 10 crates + Homebrew formula + GH Release asset bundle

🤖 Generated with Claude Code

TechAlchemistX and others added 2 commits April 19, 2026 14:52
Bump workspace version 0.3.0-alpha.0 → 0.3.0 and stamp CHANGELOG
[0.3.0] with 2026-04-19. Aggregate-release posture locked during
the v0.2.1 → v0.2.7 dev-only series comes home: every internal
patch on that cycle ships as part of this single cohesive v0.3.0
publish. Last public release was v0.2.0 (2026-04-18); v0.2.x
patches were dev-merged without separate crates.io / Homebrew /
GH Release publishes.

Scope at tag time:

- 2 new backends: secretenv-backend-gcp, secretenv-backend-azure
- Canonical #key=value fragment grammar (v0.2.1)
- Strict-mode mock retrofit across all backends (v0.2.2 → v0.2.7)
- Phase 0 groundwork: factory_helpers, check_extensive trait
  default, parallel check() via tokio::join!
- v0.3 closing-audit fixes + items 18-20 (Rule refactor, IndexMap
  fragment_directives, with_stdin_fragment chainable)
- MIT → AGPL-3.0-only relicense + Individual CLA

Gates at tag-ready state: fmt ✅ clippy ✅ test ✅ (442/442)
deny ✅ audit ✅ integration smoke ✅ (250/250 across 7 live
backends: aws-ssm, aws-secrets, 1password, vault, gcp, azure,
local).

Next: squash-merge this release PR, tag v0.3.0 signed on the
resulting main commit, push tag → release workflow publishes 10
crates to crates.io + Homebrew formula + GH Release asset bundle.

Signed-off-by: Mandeep Patel <mandeep@techalchemist.io>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Signed-off-by: TechAlchemistX <mandeep@techalchemist.io>
The `cargo publish` batch in release.yml was a carry-over from v0.2
(5 backends). v0.3 adds two more — secretenv-backend-gcp and
secretenv-backend-azure — and they must publish on the v0.3.0 tag.
Appended to the existing sequential batch; the 45s inter-stage
sleep between backend-publish and CLI-publish stays sufficient for
crates.io indexing.

Signed-off-by: Mandeep Patel <mandeep@techalchemist.io>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Signed-off-by: TechAlchemistX <mandeep@techalchemist.io>
@TechAlchemistX TechAlchemistX merged commit be27ede into main Apr 19, 2026
7 checks passed
@TechAlchemistX TechAlchemistX deleted the chore/v0.3.0-release branch April 19, 2026 18:58
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