Skip to content

chore(release): bump workspace to v0.4.0#68

Merged
P4suta merged 2 commits into
mainfrom
release/v0.4.0
Jun 14, 2026
Merged

chore(release): bump workspace to v0.4.0#68
P4suta merged 2 commits into
mainfrom
release/v0.4.0

Conversation

@P4suta

@P4suta P4suta commented Jun 14, 2026

Copy link
Copy Markdown
Owner

Pre-1.0 minor bump 0.3.0 → 0.4.0 to cut the next afm release,
tracking the freshly released aozora v0.4.0.

Changes (release bookkeeping only — no afm source changes):

  • bump afm workspace version 0.3.0 → 0.4.0
  • sync the umbrella aozora pin (and the cargo-fuzz pin) to the
    released aozora v0.4.0 commit df0f64b (tagged + provenance-
    attested), and bump the version = "0.4.0" constraint to match
  • promote CHANGELOG.md [Unreleased][0.4.0] - 2026-06-14

⚠️ Reviewer note — CHANGELOG completeness: the [Unreleased]
section is hand-curated. I promoted the heading and preserved all
existing content, but did not backfill the most recent commits
(#57#67: later playground features, fix(security) deep-nesting
stack-overflow #65, build provenance attestation #64/#66). Add any
user-facing entries you want under [0.4.0] before merge.

just check passes against aozora 0.4.0. After merge: tag v0.4.0
on main → release.yml builds the three target binaries + attests
build provenance.

🤖 Generated with Claude Code

P4suta added 2 commits June 14, 2026 15:22
Pre-1.0 minor bump (0.3.0 -> 0.4.0). Sync the umbrella aozora pin (and the cargo-fuzz pin) to the released aozora v0.4.0 commit df0f64b1a42897030d4b7d0129fb7564e070ab73 so afm v0.4.0 tracks a tagged + provenance-attested aozora rather than a loose mid-stream rev.
@P4suta P4suta merged commit b2dcf36 into main Jun 14, 2026
23 checks passed
@P4suta P4suta deleted the release/v0.4.0 branch June 14, 2026 06:30
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