Repository navigation
Update @actions/cache and @actions/artifact, stop ignoring them in Dependabot - #978
Merged
Merged
Conversation
…pendabot Bumps @actions/cache 6.0.0 -> 6.0.1 and @actions/artifact 6.1.0 -> 6.2.1, and removes the Dependabot ignore rules for both so they are maintained automatically going forward. The cache ignore was originally in place out of concern for keeping versions aligned with the vendored gradle-actions-caching library. That alignment is not required: the vendored bundle inlines its own (patched) @actions/cache and exposes a type-clean API, while this repo's direct @actions/cache usage is a separate, unpatched copy using the stock string-returning API. There is no cross-repo sync requirement, so these can be updated normally. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
@actions/cache6.0.0 → 6.0.1@actions/artifact6.1.0 → 6.2.1ignorerules for both so they're maintained automatically going forwardWhy
Both deps were excluded from Dependabot's automatic updates:
*actions/cache*was fully ignored, and*actions/artifact*had major/minor bumps ignored. Neither restriction is necessary.The
cacheignore existed out of concern for keeping versions aligned with the vendoredgradle-actions-cachinglibrary. That alignment isn't required:sources/vendor/gradle-actions-caching/index.js) inlines its own (patched)@actions/cacheand exposes a type-clean API (restore/save) that never leaks@actions/cachetypes across the boundary.@actions/cacheusage is a separate, unpatched copy consumed via the stock string-returning API (cache-service-basic.ts,provision.ts), with nopatch-package/postinstallin this repo.So there's no cross-repo sync requirement — these can be updated like any other dependency.
Verification
npm install --package-lock-onlyregenerated the lockfile (resolves cache 6.0.1, artifact 6.2.1)./buildpasses cleanThe root
dist/directory is intentionally left for the CI workflow to update.🤖 Generated with Claude Code