update

.github/workflows/release.yml

@@ -117,6 +117,10 @@ jobs:
       - uses: actions/checkout@v4
         with:
           submodules: recursive
+      - uses: swatinem/rust-cache@v2
+        with:
+          key: ${{ join(matrix.targets, '-') }}
+          cache-provider: ${{ matrix.cache_provider }}
       - name: Install cargo-dist
         run: ${{ matrix.install_dist }}
       # Get the dist-manifest

Cargo.toml

@@ -65,7 +65,7 @@ lto = true
 
 # Config for 'cargo dist'
 [workspace.metadata.dist]
-# Which actions to run on pull requests (pr-run-mode = "upload" will run the release pipeline on pull request, good for debugging and developing on release methods)
+# Which actions to run on pull requests
 pr-run-mode = "upload"
 # The preferred cargo-dist version to use in CI (Cargo.toml SemVer syntax)
 cargo-dist-version = "0.22.1"

README.md

@@ -44,4 +44,13 @@ cargo dist init
 ```
 ... And then following the instructions/prompts.
 
-A (very complicated) [release.yml](.github/workflows/release.yml) is generated and metadata is added to [Cargo.toml](Cargo.toml), if distributing for windows, a [main.wxs](wix/main.wxs) is also generated. To update these with changes to the project, simply rerun `cargo dist init`, don't edit the workflow manually, there's a [section on CI customization](https://opensource.axo.dev/cargo-dist/book/ci/customizing.html) in the `cargo dist` docs.
+A (very complicated) [release.yml](.github/workflows/release.yml) is generated and metadata is added to [Cargo.toml](Cargo.toml), if distributing for windows, a [main.wxs](wix/main.wxs) is also generated. To update these with changes to the project, simply rerun `cargo dist init`, don't edit the workflow manually, there's a [section on CI customization](https://opensource.axo.dev/cargo-dist/book/ci/customizing.html) in the `cargo dist` docs.
+
+When developing/trouble shooting the release pipeline adding `pr-run-mode = "upload"` like this
+
+```toml
+[workspace.metadata.dist]
+pr-run-mode = "upload"
+```
+
+Will run the release pipeline on pull request, then you can open a PR and develop/fix/test the release pipeline.