Trigger v0.7 compiler release

.github/workflows/ci.yml

@@ -113,11 +113,14 @@ jobs:
           cargo make check --tests
       - name: Test
         run: |
-          cargo make test -E 'not (package(miden-integration-tests) or package(miden-integration-node-tests) or package(cargo-miden))'
+          cargo make test -E 'not (package(miden-integration-tests) or package(midenc-integration-network-tests) or package(cargo-miden))'
 
-  check_release:
-    name: release checks
+  lit_tests:
+    name: midenc lit/filecheck tests
     runs-on: ubuntu-latest
+    # We only want to run our lit tests if the unit tests pass, and that has the added
+    # benefit that we can re-use the cache from the unit test job
+    needs: [unit_tests]
     steps:
       - uses: actions/checkout@v5
       - uses: ./.github/actions/cleanup-runner
@@ -128,25 +131,18 @@ jobs:
       - name: Cache Cargo
         uses: Swatinem/rust-cache@v2
         with:
-          # NOTE: We use a different cache for the these release checks
-          shared-key: ${{ github.workflow }}-shared-release-checks
+          # NOTE: We use a different cache for the tests, so they can be run in parallel, but we
+          # also share the cache for the tests for efficiency
+          shared-key: ${{ github.workflow }}-shared-tests
           prefix-key: ${{ env.RUST_CACHE_KEY }}
-          save-if: ${{ github.ref == 'refs/heads/next' }}
       - name: Install cargo-make
         run: |
           if ! cargo make --version 2>/dev/null; then
             cargo install cargo-make --force
           fi
-      - name: Check(release)
-        # We run `check` with `--release` to check the release build (without
-        # `debug_assertions`, etc.)
-        run: |
-          cargo make check --release --tests
-      - name: Check each member (release)
-        # To uncover any compilation errors hidden by the workspace feature
-        # unification and avoid surprises on publishing the crates.
+      - name: Test
         run: |
-          cargo make check-each --release --all-features
+          cargo make test-lit
 
   midenc_integration_tests:
     name: midenc integration tests
@@ -294,7 +290,7 @@ jobs:
           fi
       - name: Test
         run: |
-          cargo make test -E 'test(test_all_templates_and_examples)'
+          cargo make test -E 'test(test_all_templates)'
 
   miden_integration_node_tests:
     name: miden integration node tests
@@ -323,7 +319,40 @@ jobs:
           fi
       - name: Test
         run: |
-          cargo make test -E 'package(miden-integration-node-tests)'
+          cargo make test -E 'package(midenc-integration-network-tests)'
+
+  check_release:
+    name: release checks
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v5
+      - uses: ./.github/actions/cleanup-runner
+      - name: Install Rust
+        run: |
+          rustup update --no-self-update
+          rustc --version
+      - name: Cache Cargo
+        uses: Swatinem/rust-cache@v2
+        with:
+          # NOTE: We use a different cache for the these release checks
+          shared-key: ${{ github.workflow }}-shared-release-checks
+          prefix-key: ${{ env.RUST_CACHE_KEY }}
+          save-if: ${{ github.ref == 'refs/heads/next' }}
+      - name: Install cargo-make
+        run: |
+          if ! cargo make --version 2>/dev/null; then
+            cargo install cargo-make --force
+          fi
+      - name: Check(release)
+        # We run `check` with `--release` to check the release build (without
+        # `debug_assertions`, etc.)
+        run: |
+          cargo make check --release --tests
+      - name: Check each member (release)
+        # To uncover any compilation errors hidden by the workspace feature
+        # unification and avoid surprises on publishing the crates.
+        run: |
+          cargo make check-each --release --all-features
 
   cargo_publish_dry_run:
     name: cargo publish dry run

.github/workflows/release.yml

@@ -46,14 +46,22 @@ jobs:
 
   upload-artifacts:
     name: upload pre-built midenc executable artifacts
-    runs-on: ubuntu-latest
     needs: publish
     if: ${{ github.repository_owner == '0xMiden' && needs.publish.outputs.releases_created == 'true' }}
     permissions:
       contents: write
+      id-token: write
+      attestations: write
     strategy:
       matrix:
+        os: [macos-latest, ubuntu-latest]
         target: [aarch64-apple-darwin, x86_64-unknown-linux-gnu]
+        exclude:
+          - os: macos-latest
+            target: x86_64-unknown-linux-gnu
+          - os: ubuntu-latest
+            target: aarch64-apple-darwin
+    runs-on: ${{ matrix.os }}
     steps:
       - *checkout
       - *install-rust
@@ -91,16 +99,30 @@ jobs:
           ARGS="--release --target ${{ matrix.target }}"
           cargo make --profile production midenc ${ARGS}
           cargo make --profile production cargo-miden ${ARGS}
+      - name: prepare artifacts
+        if: ${{ steps.midenc-release.outputs.release_tag != '' }}
+        run: |
+          set -e
+          mv bin/midenc midenc-${{ matrix.target }}
+          mv bin/cargo-miden cargo-miden-${{ matrix.target }}
+      - name: attest midenc
+        if: ${{ steps.midenc-release.outputs.release_tag != '' }}
+        uses: actions/attest-build-provenance@v3
+        with:
+          subject-path: midenc-${{ matrix.target }}
+      - name: attest cargo-miden
+        if: ${{ steps.midenc-release.outputs.release_tag != '' }}
+        uses: actions/attest-build-provenance@v3
+        with:
+          subject-path: cargo-miden-${{ matrix.target }}
       - name: upload
         if: ${{ steps.midenc-release.outputs.release_tag != '' }}
         env:
           RELEASE_TAG: ${{ steps.midenc-release.outputs.release_tag }}
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
         run: |
           set -e
-          mv bin/midenc midenc-${{ matrix.target }}
           gh release upload ${RELEASE_TAG} midenc-${{ matrix.target }}
-          mv bin/cargo-miden cargo-miden-${{ matrix.target }}
           gh release upload ${RELEASE_TAG} cargo-miden-${{ matrix.target }}
 
   release:

.gitignore

@@ -1,6 +1,7 @@
 target/
-bin/midenc
-bin/litcheck
+bin/*
+!bin/filecheck
+!bin/lit
 .crates.toml
 .crates2.json
 

CONTRIBUTING.md

@@ -4,18 +4,44 @@ TBD
 
 ## Release Process
 
-### 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. Release of the Miden SDK crates
 
 1. Create a release PR against the `next` branch naming the branch with the `release-plz-` prefix (its important to use this prefix to trigger the crate publishing on CI in the later step).
 2. Manually bump ALL the SDK crate versions and update the `sdk/sdk/CHANGELOG.md`
 3. Review the changes in the release PR,  and merge it into the `next` branch.
 4. The CI will automatically run `release-plz release` after the release PR is merged to publish the new versions to crates.io.
+
+### 2. Release of the Miden Compiler
+
+1. Update the contract templates at https://github.com/0xMiden/project-template (see 2.1 below).
+2. Update the new project template at https://github.com/0xMiden/project-template (see 2.2 below).
+3. Merging to `main` will create a new release PR containing any unreleased changes.
+4. Optional. Change the proposed crate version, CHANGELOG edits.
+5. The release PR gets merged to `main` when we are ready to publish the release.
+6. The crates are published to crates.io, a new git tag is created, as well as a GitHub release
+7. A job is run to pre-build the executable for our supported targets and upload them to the created Github release.
+8. Merge the `main` branch back to the `next` branch.
+
+### 2.1. Updating the new contract templates
+
+1. Bump the Miden SDK version in the Cargo.toml.
+2. Migrate the code in lib.rs.
+3. Create a git tag.
+4. Make a PR in the compiler repo and set the new git tag (bump the current in `PROJECT_TEMPLATES_REPO_TAG` at tools/cargo-miden/src/commands/new_project.rs).
+5. Run the compiler tests, if red then goto 2.
+
+### 2.2. Updating the new project template
+
+1. Bump the Miden SDK, `miden-client` versions in the Cargo.toml files, set the `cargo-miden` version to the `next` branch for now(after the compiler release it'd be the new version).
+2. Migrate the code in the contracts, tests and the app.
+3. Create a git tag.
+4. Make a PR in the compiler repo and set the new git tag (bump the current in `MIDEN_PROJECT_TEMPLATE_REPO_TAG` at tools/cargo-miden/src/commands/new_project.rs).
+5. Run the local repo tests, if red then goto 2.
+6. Run the compiler tests, if red then goto 2.
+
+### 3. After the Miden Compiler crates are published
+
+1. Change the `cargo-miden` version to the newly published crate in the PR (created in 2.2.4) at https://github.com/0xMiden/project-template.
+2. Re-set the same git tag (created in 2.2.3) to the new commit.
+3. Merge the PR (created in 2.2.4).
+