Skip to content

ci: bump actions/cache from 4 to 6 - #2

Merged
a9lim merged 3 commits into
mainfrom
dependabot/github_actions/actions/cache-6
Aug 4, 2026
Merged

ci: bump actions/cache from 4 to 6#2
a9lim merged 3 commits into
mainfrom
dependabot/github_actions/actions/cache-6

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 3, 2026

Copy link
Copy Markdown
Contributor

Bumps actions/cache from 4 to 6.

Release notes

Sourced from actions/cache's releases.

v6.0.0

What's Changed

Full Changelog: actions/cache@v5...v6.0.0

v5.1.0

What's Changed

Full Changelog: actions/cache@v5...v5.1.0

v5.0.5

What's Changed

Full Changelog: actions/cache@v5...v5.0.5

v5.0.4

What's Changed

New Contributors

Full Changelog: actions/cache@v5...v5.0.4

v5.0.3

What's Changed

Full Changelog: actions/cache@v5...v5.0.3

v.5.0.2

v5.0.2

What's Changed

... (truncated)

Changelog

Sourced from actions/cache's changelog.

Releases

How to prepare a release

[!NOTE] Relevant for maintainers with write access only.

  1. Switch to a new branch from main.
  2. Run npm test to ensure all tests are passing.
  3. Update the version in https://github.com/actions/cache/blob/main/package.json.
  4. Run npm run build to update the compiled files.
  5. Update this https://github.com/actions/cache/blob/main/RELEASES.md with the new version and changes in the ## Changelog section.
  6. Run licensed cache to update the license report.
  7. Run licensed status and resolve any warnings by updating the https://github.com/actions/cache/blob/main/.licensed.yml file with the exceptions.
  8. Commit your changes and push your branch upstream.
  9. Open a pull request against main and get it reviewed and merged.
  10. Draft a new release https://github.com/actions/cache/releases use the same version number used in package.json
    1. Create a new tag with the version number.
    2. Auto generate release notes and update them to match the changes you made in RELEASES.md.
    3. Toggle the set as the latest release option.
    4. Publish the release.
  11. Navigate to https://github.com/actions/cache/actions/workflows/release-new-action-version.yml
    1. There should be a workflow run queued with the same version number.
    2. Approve the run to publish the new version and update the major tags for this action.

Changelog

6.1.0

6.0.0

  • Updated @actions/cache to ^6.0.1, @actions/core to ^3.0.1, @actions/exec to ^3.0.0, @actions/io to ^3.0.2
  • Migrated to ESM module system
  • Upgraded Jest to v30 and test infrastructure to be ESM compatible

5.0.4

  • Bump minimatch to v3.1.5 (fixes ReDoS via globstar patterns)
  • Bump undici to v6.24.1 (WebSocket decompression bomb protection, header validation fixes)
  • Bump fast-xml-parser to v5.5.6

5.0.3

5.0.2

... (truncated)

Commits
  • 55cc834 Merge pull request #1768 from jasongin/readonly-cache
  • d8cd72f Bump @​actions/cache to v6.1.0 - handle cache write error due to RO token
  • 2c8a9bd Merge pull request #1760 from actions/samirat/esm_migration_and_package_update
  • e9b91fd Prettier fixes
  • e4884b8 Rebuild dist
  • 10baf01 Fixed licenses
  • e39b386 Fix test mock return order
  • b692820 PR feedback
  • 6074912 Rebuild dist bundles as ESM to match type:module
  • 5a912e8 Fix lint and jest issues
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot 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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [actions/cache](https://github.com/actions/cache) from 4 to 6.
- [Release notes](https://github.com/actions/cache/releases)
- [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md)
- [Commits](actions/cache@v4...v6)

---
updated-dependencies:
- dependency-name: actions/cache
  dependency-version: '6'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Aug 3, 2026
@a9lim
a9lim merged commit ca3019a into main Aug 4, 2026
7 checks passed
@dependabot
dependabot Bot deleted the dependabot/github_actions/actions/cache-6 branch August 4, 2026 18:26
a9lim added a commit that referenced this pull request Aug 9, 2026
… W7; typed fragment

Fresh audit #1 (sol-tier, threadless): physics CONFIRMED-SOUND, but
two countermodels (WF fire collision; Pα post-erasure re-seek under
an admitted certificate), an instance-key injectivity gap, a fuzzed
duplicate fresh call via alpha-decode, and honesty defects. All
reproduced locally before correction.

v1.8 (kernel.md §15): certified erasure leaves branch-consistent
decode records; the refire guard makes one-fire-per-instance a
runtime machine invariant (v1.7's alpha-cargo compile-time
obligation discharged and deleted); discover_total validates its
fixpoint and refuses unsound certificates (Pα heals to {1/4, 3/4}
via the conservative fallback); W7 fibre coherence + mechanized
range disjointness; typecheck.py = the typed h-only fragment
judgment (15/18; q itself untypable — qprime is its repair). The
sixteen stay marginal-, support-, and basis-identical. Auditor's
reproducer reruns clean; fuzz 250/250. PASS re-claim gated on
fresh audit #2.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
a9lim added a commit that referenced this pull request Aug 9, 2026
…ed, W registered placement-open

Fresh audit #2 FAILed v1.9 (the W fatal witness: clean validation,
wrong physics — a zero-amplitude structural refire vetoing B's
coherence-restoring certificate; W8 preservation; (e) grouping;
checker totality). Working-thread verdict on the design fork:
amplitudes decide run success, never isometry; no bare-term ideal
oracle exists. v1.10: structural admission/isometry mandatory +
per-step dynamic cleanliness of the frozen certificate;
instance-directed erasure (popkeys/spectators) with
validation-adjudicated admission; deep W3 + key-state algebra;
machine_coverage + written-first physics table. B heals to
{halt1: 1}; W measured inexpressible (staged uncomputation) and
registered as the standing placement limitation. Twenty programs
green; sixteen bit-identical since v1.7.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
a9lim added a commit that referenced this pull request Aug 10, 2026
…ts its second witness

Audit #33 (cx-20260810-093110-a5e9) FAILED v1.40 on the scope
statement itself — the machine clean a SEVENTEENTH consecutive
round. One round after shrinking the claim, "extensional verdicts"
was one word too strong: the genuine gates check PREDICATES
(sens28 is 'W0'-absence; genuine comp28's actual verdict is
['W2-dup']x11), and deleting the sole W2-dup append flips the
checker from rejecting to accepting a fixed genuine fixture with
the full suite green — no fixture awareness needed.

v1.41 — claim language only; gates, fixtures, machine untouched;
wf.py AST-identical again:
- §10's scope statement now ENUMERATES the gated predicates
  clause-by-clause (verified against the source), with the reason
  the by-design-dup families gate W0-freeness only
- audit #33's W2-dup countermodel registered as BOUNDARY WITNESS #2
  (the predicate-vs-verdict gap) beside the fixture-aware mutant;
  their reproducer joins the roster as kit 24, both witness rows
  exit 0 BY CONSTRUCTION
- three wf.py "pins ... verdicts" comments -> "gates the stated
  predicates"; v1.39/v1.40 chronicle rows corrected with attribution
- the decruft-script hazard closed the STRONGER way: the idempotence
  check swept 36 current-generation artifacts (all restored, both
  directions in the MANIFEST) proving the script generation-pinned,
  so it is RETIRED behind a mechanical historical guard; the
  KEEP_EXACT-suffices prediction marked as a miss
- all captures byte-identical (conservation suffix aside); 24-kit
  battery at adjudicated readings; forcings 7/7 (reduced, disclosed)

Fresh audit #34 launched (cx-20260810-101610-734d, 1,048,703-byte
pack); the PASS re-claim stays gated on it.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant