Skip to content

chore: update dist to 0.32.0#202

Merged
untitaker merged 1 commit into
untitaker:mainfrom
potiuk:update-dist-0.32.0
Jun 27, 2026
Merged

chore: update dist to 0.32.0#202
untitaker merged 1 commit into
untitaker:mainfrom
potiuk:update-dist-0.32.0

Conversation

@potiuk

@potiuk potiuk commented Jun 27, 2026

Copy link
Copy Markdown
Contributor

Bump cargo-dist-version from 0.30.2 to 0.32.0 and regenerate release.yml with the matching dist binary (dist generate --check passes).

Picked up from the 0.32.0 CI template:

  • action pin bumps: checkout@v6, upload-artifact@v7, download-artifact@v8, setup-node@v6
  • attestation step switched from actions/attest-build-provenance@v2 to actions/attest@v4

Generated-by: Claude Opus 4.8 (1M context)

Bump `cargo-dist-version` from 0.30.2 to 0.32.0 and regenerate the release
workflow with the matching `dist` binary. Picks up the 0.32.0 CI template:
updated checkout/upload-artifact/download-artifact/setup-node action pins and
the switch from actions/attest-build-provenance@v2 to actions/attest@v4.

Generated-by: Claude Opus 4.8 (1M context)
@untitaker untitaker merged commit 50811b9 into untitaker:main Jun 27, 2026
12 checks passed
@potiuk

potiuk commented Jun 27, 2026

Copy link
Copy Markdown
Contributor Author

I also tested it in my PR before :) and release (failed on push docker and npm, but the test installation workflow and steps before worked.

Nice to not see the warnings any more.

Was just about to tell you that it's safe to merge :)

BTW. We have few days cooldown for our dependabot. So I will confirm that everything works after it passes.

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