Skip to content

Bump actions/cache from 5 to 6#123

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions/cache-6
Closed

Bump actions/cache from 5 to 6#123
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions/cache-6

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 23, 2026

Copy link
Copy Markdown
Contributor

Bumps actions/cache from 5 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.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

When creating cache entries, 429s returned from the cache service will not be retried.

v5.0.1

[!IMPORTANT] actions/cache@v5 runs on the Node.js 24 runtime and requires a minimum Actions Runner version of 2.327.1.

... (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.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

  • Bump @actions/cache to v5.0.3 #1692

5.0.1

... (truncated)

Commits

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 5 to 6.
- [Release notes](https://github.com/actions/cache/releases)
- [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md)
- [Commits](actions/cache@v5...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 Jun 23, 2026
@dependabot dependabot Bot requested a review from a team as a code owner June 23, 2026 15:33
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Jun 23, 2026
kishore7snehil added a commit that referenced this pull request Jun 25, 2026
Update GitHub Actions pins across the workflows: actions/checkout v6 to v7
(publish, test, codeql) and actions/cache v5 to v6 (test). Supersedes #121,
#123.
kishore7snehil added a commit that referenced this pull request Jun 25, 2026
…gation/impersonation (#122)

* feat: validate CTE actor token pairing and surface act claim for delegation

* fix(cte): harden act-claim extraction against decode and issuer failures

The act-claim enrichment in custom_token_exchange ran _verify_and_decode_jwt
with no error handling, so a present-but-undecodable id_token turned an
already-issued exchange into a generic TOKEN_EXCHANGE_FAILED. It also skipped
the normalized issuer check the login path applies before trusting claims.

Wrap the enrichment so any decode/verify failure leaves act=None instead of
failing the exchange, and apply the issuer check before reading the claim.
Rewrite the opaque-token test (it never exercised the decode path) and add
coverage for the undecodable-id_token and issuer-mismatch cases.

* fix(cte): validate subject_token_type and actor_token, clarify act sourcing

Add local empty/whitespace guards for subject_token_type and actor_token so
they fail with a clear INVALID_TOKEN_FORMAT instead of a generic round-trip
error from the token endpoint, matching the existing subject_token check.
Add tests for both cases.

Document that response.act is read from the id_token and that Auth0 writes
the same act onto the access token (verified against the platform token
dialects), noting the access token may be opaque. Add a comment on the login
path noting act reaches the session user via UserClaims. Rename the refresh
test to reflect that it pins the state-merge behavior the refresh path uses.

* chore(deps): bump idna, pyjwt, pydantic, and ruff in poetry.lock

Refresh the lock for the open dependabot pip bumps in one go: idna 3.13 to
3.18, pyjwt 2.12.1 to 2.13.0, pydantic 2.13.3 to 2.13.4 (pydantic-core
2.46.4), and ruff 0.15.11 to 0.15.19. All within the existing pyproject
constraints; full suite passes. Supersedes #110, #113, #118, #119.

* ci: bump actions/checkout to v7 and actions/cache to v6

Update GitHub Actions pins across the workflows: actions/checkout v6 to v7
(publish, test, codeql) and actions/cache v5 to v6 (test). Supersedes #121,
#123.
@dependabot @github

dependabot Bot commented on behalf of github Jun 25, 2026

Copy link
Copy Markdown
Contributor Author

Looks like actions/cache is up-to-date now, so this is no longer needed.

@dependabot dependabot Bot closed this Jun 25, 2026
@dependabot dependabot Bot deleted the dependabot/github_actions/actions/cache-6 branch June 25, 2026 08:51
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.

0 participants