chore: Cherry-pick changes from upstream

.github/workflows/auto_cherry_pick.yml

@@ -11,6 +11,10 @@ on:
         description: "Specify Node.js version (e.g., '18', '20', 'lts/*')"
         required: false
         default: "24"
+      mode:
+        description: "Run mode: cherry-pick or verify"
+        required: false
+        default: "cherry-pick"
   pull_request:
     types: [opened, synchronize, labeled]
 
@@ -22,11 +26,11 @@ permissions:
 
 jobs:
   cherry-pick:
-    if: github.event_name == 'workflow_dispatch' || contains(fromJson(toJson(github.event.pull_request.labels)).*.name, 'review-required')
-    uses: step-security/reusable-workflows/.github/workflows/auto_cherry_pick.yaml@fix_Verify_cherry_pick-Logic
+    if: (github.event_name == 'workflow_run' && github.event.workflow_run.conclusion == 'success') || github.event_name == 'workflow_dispatch' || contains(fromJson(toJson(github.event.pull_request.labels)).*.name, 'review-required')
+    uses: step-security/reusable-workflows/.github/workflows/auto_cherry_pick.yaml@v1
     with:
       original-owner: "Swatinem"
       repo-name: "rust-cache"
       base_branch: ${{ inputs.base_branch }}
-      mode: ${{ github.event_name == 'pull_request' && 'verify' || inputs.mode }}
+      mode: ${{ github.event_name == 'pull_request' && 'verify' || inputs.mode || 'cherry-pick' }}
       node_version: "${{ inputs.node_version || '24' }}"

.github/workflows/buildjet.yml → .github/workflows/warpbuild.yml

@@ -1,6 +1,6 @@
-name: buildjet
+name: warpbuild
 
-on: 
+on:
   push:
     branches: ["main"]
   pull_request:
@@ -9,13 +9,13 @@ on:
 permissions: {}
 
 jobs:
-  buildjet:
+  warpbuild:
     strategy:
       fail-fast: false
       matrix:
         os: ${{ github.actor == 'dependabot[bot]' && fromJSON('["ubuntu-latest"]') || fromJSON('["ubuntu-latest", "macos-latest", "windows-latest"]') }}
 
-    name: Test buildjet provider on ${{ matrix.os }}
+    name: Test warpbuild provider on ${{ matrix.os }}
     runs-on: ${{ matrix.os }}
 
     env:
@@ -36,7 +36,7 @@ jobs:
       - uses: ./
         with:
           workspaces: tests
-          cache-provider: buildjet
+          cache-provider: warpbuild
 
       - run: |
           cargo check

.gitignore

@@ -6,3 +6,4 @@ target/
 
 # Mac
 .DS_Store
+.build

.npmrc

@@ -0,0 +1 @@
+min-release-age=3

README.md

@@ -8,7 +8,7 @@ sensible defaults.
 ## Example usage
 
 ```yaml
-- uses: actions/checkout@v5
+- uses: actions/checkout@v7
 
 # selecting a toolchain either by action or manual `rustup` calls should happen
 # before the plugin, as the cache uses the current rustc version as its cache key
@@ -34,7 +34,7 @@ sensible defaults.
     # default: "true"
     add-job-id-key: ""
 
-    # Weather the a hash of the rust environment should be included in the cache key.
+    # Whether the a hash of the rust environment should be included in the cache key.
     # This includes a hash of all Cargo.toml/Cargo.lock files, rust-toolchain files,
     # and .cargo/config.toml files (if present), as well as the specified 'env-vars'.
     # default: "true"
@@ -94,7 +94,7 @@ sensible defaults.
     lookup-only: ""
 
     # Specifies what to use as the backend providing cache
-    # Can be set to "github", "buildjet", or "warpbuild"
+    # Can be set to "github", or "warpbuild"
     # default: "github"
     cache-provider: ""
 
@@ -144,7 +144,7 @@ This action currently caches the following files/directories:
 This cache is automatically keyed by:
 
 - the github [`job_id`](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_id)
-(if `add-job-id-key` is `"true"`),
+  (if `add-job-id-key` is `"true"`),
 - the rustc release / host / hash (for all installed toolchains when
   available),
 - the following values, if `add-rust-environment-hash-key` is `"true"`:
@@ -212,5 +212,5 @@ to see those details as well as further details related to caching operations.
 - The cache cleaning process currently removes all the files from `~/.cargo/bin`
   that were present before the action ran (for example `rustc`), by default.
   This can be an issue on long-running self-hosted runners, where such state
-  is expected to be preserved across runs.  You can work around this by setting
+  is expected to be preserved across runs. You can work around this by setting
   `cache-bin: "false"`.

action.yml

@@ -48,7 +48,7 @@ inputs:
     required: false
     default: "true"
   cache-provider:
-    description: "Determines which provider to use for caching. Options are github, buildjet, or warpbuild. Defaults to github."
+    description: "Determines which provider to use for caching. Options are github, or warpbuild. Defaults to github."
     required: false
     default: "github"
   cache-bin:
@@ -68,8 +68,8 @@ outputs:
     description: "A boolean value that indicates an exact match was found."
 runs:
   using: "node24"
-  main: "dist/restore/index.js"
-  post: "dist/save/index.js"
+  main: "dist/restore.js"
+  post: "dist/save.js"
   post-if: "success() || env.CACHE_ON_FAILURE == 'true'"
 branding:
   icon: "archive"