Repository navigation
chore(deps): bump actions/cache/save from 4.3.0 to 6.1.0 - #289
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [actions/cache/save](https://github.com/actions/cache) from 4.3.0 to 6.1.0. - [Release notes](https://github.com/actions/cache/releases) - [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md) - [Commits](actions/cache@0057852...55cc834) --- updated-dependencies: - dependency-name: actions/cache/save dependency-version: 6.1.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
|
Dependabot opened #287, #288, #289 and #290 within an hour of each other. Three of them move an action to the exact SHA this repository already uses elsewhere, so they are one change - 'use the version already pinned' - and merging them separately costs three serialised runs of the full suite on main (Julia tests alone is 20-35 minutes), plus a rebase of the remaining two after each merge. - actions/cache/restore and actions/cache/save 4.3.0 -> 6.1.0, the SHA actions/cache is already pinned at in six places. - actions/upload-artifact 4.6.2 -> 7.0.2, the SHA already pinned in four. - upload-sarif's comment claimed v4.38.0 and '4.38.1 blocked estate-wide', while the pinned SHA actually resolves to v4.39.0 on Dependabot's reading, so the note described a version the pin was already past. The comment now states what is true and why the SHA rather than the tag is the pin. github/codeql-action is now ignored by Dependabot: a pin that carries an estate-wide decision should be moved by hand with its comment, not silently. That leaves #290 (4.39.0 -> 4.39.1) as the owner's call rather than a bot's. Co-authored-by: arena-agent <297053741+arena-agent@users.noreply.github.com>
|
Folded into #292, which lands the same pin alignment in one change. Three pull requests that each move an action to the exact SHA this repository already pins elsewhere are one change, and merging them one at a time costs three serialised runs of the full suite on
Nothing is lost: the diff is preserved in #292 and recoverable at |
…292) ## Change and reason Dependabot opened **four pull requests in an hour** (#287, #288, #289, #290). Three of them move an action to the **exact SHA this repository already pins elsewhere**, so they are one change — "use the version already in use" — and merging them one at a time costs three serialised runs of the full suite on `main` (`Julia tests` alone is 20–35 min), plus a rebase of the remaining two after each merge. This does the three in one pass and leaves the fourth to a person. | Action | From | To | Why it is safe | | --- | --- | --- | --- | | `actions/cache/restore`, `actions/cache/save` | 4.3.0 | **6.1.0** | Same SHA `actions/cache` is already pinned at in six places in `ci.yml`. | | `actions/upload-artifact` | 4.6.2 | **7.0.2** | Same SHA already pinned in four places (`ci.yml` line 501, `hypatia-scan-reusable.yml` ×2). | | `github/codeql-action/upload-sarif` | — | unchanged | Comment corrected only: see below. | ### The one that needed reading, not merging #290 bumps `upload-sarif` "from 4.39.0 to 4.39.1", while the comment beside the pin says: ``` uses: github/codeql-action@6f2ac81f… # v4.38.0 (4.38.1 blocked estate-wide; nexia-list#100) ``` Two facts that do not fit together: Dependabot resolves the pinned SHA to **4.39.0**, so the comment was already describing a version the pin had moved past, and it still records an estate-wide block on 4.38.1. A reviewer cannot tell from the diff whether the new SHA is blocked, allowed, or something else — the comment contradicts the pin. So this PR does **not** take the 4.39.1 bump. It corrects the comment to state what is true (the SHA resolves to v4.39.0, and the SHA rather than the tag is the pin), and adds an `ignore` rule so Dependabot stops rewriting a pin that carries an estate-wide decision: ```yaml ignore: - dependency-name: github/codeql-action update-types: [version-update:semver-major, version-update:semver-minor, version-update:semver-patch] ``` #290 stays open as the owner's call: it is a patch release whose only change is the bundled CodeQL version, and whether the estate's block reaches 4.39.x is not something this repository's files can answer. ## Validation ``` bash scripts/check-governance-contract.sh # 70 checks passed (unchanged on this branch) bash scripts/tests/test-governance-contract.sh ``` All workflow files and `.github/dependabot.yml` parse as YAML, and the four changed SHAs are byte-identical to the ones already used in this repository (verified by grep, not by trust in the bot). **Not run:** the Julia and frontend suites — no Julia or TypeScript is touched. CI runs them. ## Scope Closing #287, #288 and #289 in favour of this, so the pending dependency work is one pull request instead of three. No pin moves to a SHA this repository does not already use; no `renv.lock`, `Manifest.toml` or `tool_versions.yml` change. ## Contribution checks - [x] I followed [CONTRIBUTING.md](../CONTRIBUTING.md). - [x] This branch starts at `main`'s tip and has no merge commits from it. - [x] CI has run; see checks. - [x] Existing licensing, citation and acknowledgement text is unchanged. Co-authored-by: Arena Agent <agent@arena.ai> Co-authored-by: arena-agent <297053741+arena-agent@users.noreply.github.com>



Bumps actions/cache/save from 4.3.0 to 6.1.0.
Release notes
Sourced from actions/cache/save's releases.
... (truncated)
Changelog
Sourced from actions/cache/save's changelog.
... (truncated)
Commits
55cc834Merge pull request #1768 from jasongin/readonly-cached8cd72fBump@actions/cacheto v6.1.0 - handle cache write error due to RO token2c8a9bdMerge pull request #1760 from actions/samirat/esm_migration_and_package_updatee9b91fdPrettier fixese4884b8Rebuild dist10baf01Fixed licensese39b386Fix test mock return orderb692820PR feedback6074912Rebuild dist bundles as ESM to match type:module5a912e8Fix lint and jest issuesDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)