release: prepare v0.4.1 - #14
Merged
Merged
Conversation
Patch, not a minor: the change set is additive to the Python and TypeScript bindings and leaves the public Rust API untouched, so nothing downstream on tokenfold-core = "0.4" breaks. tokenfold-core's only diff since 0.4.0 is an [[example]] declaration, which cargo publish skips with a warning. Bumps the workspace version, the inter-crate dependency pins, both lockfiles, the npm manifest and its optionalDependencies, and the version assertions in packages/tokenfold/test/api.test.mjs (both the plain string and the regex-escaped form) and scripts/stage-npm-platform-packages.test.mjs.
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
1 participant
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.
Version bump only — no behavior change. The 0.4.1 content landed in #13.
Patch rather than minor: the change set is additive to the Python and
TypeScript bindings and leaves the public Rust API untouched, so nothing
depending on
tokenfold-core = "0.4"breaks.tokenfold-core's only diffsince 0.4.0 is an
[[example]]declaration pointing out of the crate root,which
cargo publishskips with a warning — verified withcargo publish -p tokenfold-core --dry-run --lockedat the new version.Bumped:
Cargo.toml[workspace.package]version and the inter-crate dependencypins in
tokenfold-cli,tokenfold-learn,tokenfold-output,tokenfold-pyCargo.lock(cargo update -w) andpackages/tokenfold/package-lock.json(
npm install --package-lock-only)packages/tokenfold/package.jsonversion + all fiveoptionalDependenciespackages/tokenfold/test/api.test.mjs— both the plainstring and the regex-escaped
/^tokenfold 0\.4\.1/— and inscripts/stage-npm-platform-packages.test.mjsCHANGELOG.md:[Unreleased]→[0.4.1] - 2026-08-18Deliberately untouched:
eval/tasks/v04/*.json, which contains0.4.0-alphainside synthetic build-error fixture text, and the
rtk 0.4.1pins incrates/tokenfold-cli/{src,tests}/rtk.rs, which are a third-party tool'sversion. A repo-wide find-and-replace would have corrupted both.
Verified locally:
cargo fmt --check,clippy -D warnings, the rebuilt CLIreports
tokenfold 0.4.1, and the npm suite passes against it (21 pass,1 skipped).