Preparing v0.5 compiler release #752
Merged
Conversation
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
It should be managed automatically now.
fix: intra block spills rewrite to process all ops in the block
There was a case where it erroneously left the LHS on top of the stack.
Pass profile options via `--config` flag to `cargo`; Allow workspace member `cargo miden build`
chore(ci): upgrade checkout to v5
Prepare release v0.4.1 (take 2)
Since `release-plz` does not consider dev-dependencies when computing the publish order the publishing will fail for a crate that has a not-yet-published crate version in the dev-dependencies.
Apparently, `gix` fails if the registry index is present. See failed https://github.com/0xMiden/compiler/actions/runs/17444451785/job/49535289715
instead of WIT interface
instead of the WIT interface
…e`, `metadata` modules
[1/x] Account WIT interface generation
[1/x] fix: `cargo-miden` picks the correct package from cargo metadata
…-and-allo-boilerplate [2/x] feature(SDK): SDK macros generate panic handler and global allocator boilerplate
[2/x] feature: `cargo miden new` without options creates a Miden project
…input length is a multiple of 4
Use stdlib `hash_memory_words` in `hash_words` and in `hash_elements` (if multiple of 4)
The new release process will be the following: Release of the Miden Compiler 1. Merging to `main` will create a new release PR containing any unreleased changes. 2. Optional. Change the proposed crate version, CHANGELOG edits. 3. The release PR gets merged to `main` when we are ready to publish the release. 4. The crates are published to crates.io, a new git tag is created, as well as a GitHub release 5. A job is run to pre-build the executable for our supported targets and upload them to the created Github release. 6. Merge the `main` branch back to the `next` branch. Release of the Miden SDK crates 1. Create a release PR naming the branch with the `release-plz-` prefix (its important to use this prefix to trigger the crate publishing on CI in one of the next steps). 2. Bump the SDK crates versions and update the CHANGELOG. 3. Merge it into the main branch. 4. The CI will automatically run `release-plz release` after the release PR is merged to publish the new versions to crates.io. 5. Set a git tag for the published crates to mark the release. 6. Make a Github release. 7. Merge the `main` branch back to the `next` branch. Implementation details: 1. Suppress git tag and github release creation for all the crates except `midenc` and `miden`(SDK). 2. In `uploading-artifacts` CI job find the release tags for `midenc` (to ignore SDK release).
…n-debug chore: revamp the release process automation
chore: Miden SDK v0.7.0 release
…emplates chore: use v0.22.0 git tag for new project templates (SDK v0.7)
…ult-token chore: restore `GITHUB_TOKEN` in the new release CI workflow
otrho
approved these changes
Nov 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR merges the next branch into the main branch to trigger the new release workflow on CI. After this branch is merged, the new release workflow on CI will create
release-plzPR with the bumped versions and updated changelogs.