release: prepare for 0.0.6 release

.github/workflows/ci.yml

@@ -45,7 +45,7 @@ jobs:
         uses: actions-rs/cargo@v1
         with:
           command: make
-          args: test
+          args: test -E 'not package(cargo-miden)'
 
   cargo_miden_test_clean_env:
     # Run cargo-miden test in the clean env to simulate user's first run.
@@ -67,11 +67,16 @@ jobs:
             ~/.cargo/registry
             ~/.cargo/git
           key: ${{ github.workflow }}-${{ github.job }}-toolchain-${{ env.CARGO_MAKE_TOOLCHAIN }}
+      - name: Install cargo-make
+        uses: actions-rs/cargo@v1
+        with:
+          command: install
+          args: cargo-make
       - name: Test
         uses: actions-rs/cargo@v1
         with:
-          command: test
-          args: -p cargo-miden --test integration
+          command: make
+          args: test -E 'package(cargo-miden)'
 
   clippy:
     name: clippy
@@ -95,7 +100,7 @@ jobs:
         with:
           command: install
           args: cargo-make
-      - name: Test
+      - name: Run clippy
         uses: actions-rs/cargo@v1
         with:
           command: make

.github/workflows/release.yml

@@ -1,5 +1,5 @@
 # Runs `release-plz release` only after the release PR (starts with `release-plz-`) 
-# is merged to the main branch. See `release_always = false` in `release-plz.toml` 
+# is merged to the next branch. See `release_always = false` in `release-plz.toml` 
 # Publishes any unpublished crates when.
 # Does nothing if all crates are already published (i.e. have their versions on crates.io).
 # Does not create/update release PRs.
@@ -13,7 +13,7 @@ name: release-plz
 on:
   push:
     branches:
-      - main
+      - next
 
 env:
   CARGO_MAKE_TOOLCHAIN: nightly-2024-05-07
@@ -45,12 +45,3 @@ jobs:
       env:
         GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
         CARGO_REGISTRY_TOKEN: ${{ secrets.CARGO_REGISTRY_TOKEN }}
-    - name: Publish Miden SDK crates
-      uses: MarcoIeni/[email protected]
-      with:
-        # Only run the `release` command that publishes any unpublished crates.
-        command: release
-        manifest_path: sdk/Cargo.toml
-      env:
-        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        CARGO_REGISTRY_TOKEN: ${{ secrets.CARGO_REGISTRY_TOKEN }}

CONTRIBUTING.md

@@ -12,9 +12,8 @@ Install `release-plz` CLI tool following the instructions [here](https://release
 
 The release process for the Miden Compiler and Miden SDK is managed using the `release-plz` tool. The following steps outline the process for creating a new release:
 
-1. Run `release-plz update` in the repo root folder to update the compiler crates versions and generate changelogs.
-2. Run `release-plz update` in the `sdk` folder to update the SDK crates versions and generate changelogs.
-3. Create a release PR naming the branch with the `release-plz-` suffix (its important to use this suffix to trigger the crate publishing on CI in step 4).
-4. Review the changes in the release PR, commit edits if needed and merge it into the main branch.
-5. The CI will automatically run `release-plz release` after the release PR is merged to publish the new versions to crates.io.
-6. Set a git tag for the published crates to mark the release.
+1. Run `release-plz update` in the repo root folder to update the crates versions and generate changelogs.
+2. Create a release PR naming the branch with the `release-plz-` suffix (its important to use this suffix to trigger the crate publishing on CI in step 4).
+3. Review the changes in the release PR, commit edits if needed and 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.