Skip to content

chore: prepare 0.33.0 - #4547

Merged
lwshang merged 2 commits into
masterfrom
chore/prepare-0.33.0
Sep 23, 2026
Merged

lwshang merged 2 commits into
masterfrom
chore/prepare-0.33.0

Conversation

@lwshang

@lwshang lwshang commented Sep 23, 2026

Copy link
Copy Markdown
Contributor

Description

Release preparation for 0.33.0.

  • Rolls the dfx changelog: everything under # UNRELEASED becomes # 0.33.0.
  • Bumps the crates that carry the new evidence encoding, and records it in
    ic-certified-assets/CHANGELOG.md:
crate from to
ic-certified-assets 0.3.0 0.4.0
ic-asset 0.29.0 0.30.0
icx-asset 0.29.0 0.30.0

Minor is the breaking position for a 0.x crate (^0.29 resolves >=0.29.0, <0.30.0),
and all three are breaking: the encoding itself, plus the new variants on
ComputeEvidenceError and PrepareSyncForProposalError, neither of which is
#[non_exhaustive]. icx-asset moves to keep the sync its manifest documents, and the
workspace pin in Cargo.toml follows ic-asset.

dfx-core is untouched by this change and stays at 0.4.0.

The dfx version itself is not bumped here — scripts/release.sh does that on the release
branch.

How Has This Been Tested?

cargo build across the four crates and cargo test -p ic-certified-assets -p ic-asset
(110 + 30) after the bump; Cargo.lock updated via cargo update -p.

Checklist:

  • The title of this PR complies with Conventional Commits.
  • I have edited the CHANGELOG accordingly.
  • I have made corresponding changes to the documentation.

🤖 Generated with Claude Code

Roll the dfx changelog into a 0.33.0 section, and bump the crates carrying the
new evidence encoding. Minor is the breaking position for a 0.x crate, and all
three are breaking: the encoding itself, plus new variants on ComputeEvidenceError
and PrepareSyncForProposalError, neither of which is #[non_exhaustive].

  ic-certified-assets  0.3.0  -> 0.4.0
  ic-asset             0.29.0 -> 0.30.0
  icx-asset            0.29.0 -> 0.30.0   (kept in sync with ic-asset)

dfx-core is untouched by this change and stays at 0.4.0.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@lwshang
lwshang requested a review from a team as a code owner September 23, 2026 12:29
@zeropath-ai

zeropath-ai Bot commented Sep 23, 2026 •

Copy link
Copy Markdown

✅ No security or compliance issues detected. Reviewed everything up to aec3b62.

Security Overview
Detected Code Changes
Change Type Relevant files
Enhancement ► CHANGELOG.md
    Add unreleased and 0.33.0 notes for asset canister changes
Enhancement ► Cargo.toml
    ic-asset version bump to 0.30.0
Enhancement ► src/canisters/frontend/ic-asset/Cargo.toml
    version bump to 0.30.0
Enhancement ► src/canisters/frontend/ic-certified-assets/Cargo.toml
    version bump to 0.4.0
Enhancement ► src/canisters/frontend/icx-asset/Cargo.toml
    version bump to 0.30.0
Enhancement ► src/canisters/frontend/ic-certified-assets/CHANGELOG.md
    Update with 0.4.0 changes
Enhancement ► src/distributed/assetstorage.wasm.gz
    Binary asset updated

Cargo folds the package version into -C metadata, so bumping
ic-certified-assets to 0.4.0 changes the compiled wasm even though no code
changed. The version bump and the rebuilt binary have to land together, which
is what frontend-canister-up-to-date checks.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@lwshang
lwshang enabled auto-merge (squash) September 23, 2026 13:07
@lwshang
lwshang merged commit 271392a into master Sep 23, 2026
112 checks passed
@lwshang
lwshang deleted the chore/prepare-0.33.0 branch September 23, 2026 13:14
@lwshang lwshang mentioned this pull request Sep 23, 2026
2 of 3 tasks
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.

2 participants