Bump actions/cache from 4.3.0 to 6.1.0 - #2
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
dependabot
Bot
added
dependencies
Bumps [actions/cache](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 dependency-version: 6.1.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/github_actions/actions/cache-6.1.0
branch
from
September 3, 2026 17:07
8a84c49 to
0630043
Compare
Author
|
Superseded by #15. |
dependabot
Bot
deleted the
dependabot/github_actions/actions/cache-6.1.0
branch
September 4, 2026 15:56
karthik1729
added a commit
that referenced
this pull request
Sep 12, 2026
…team The create, clone, restore and push gates charged a team workspace to the team, but the object was stamped with the person who made it (`spec.owner`) plus `spec.team`, and `usage` summed `spec.owner` alone — so a team's workspaces, disk and snapshots were counted against no one, and a member could allocate past any limit. `usage` now reads the team label as well as the owner label and charges each object by one rule: `spec.team` when set, else `spec.owner`; a snapshot follows its volume, and only a snapshot whose volume is in no listing falls back to its own owner. The admin owners page's fold uses the same rule and the same per-item accounting as the gate (the hidden builder spends no environment slot; a service's own resources beat the unit), so a grant made off that page is made off the number the gate enforces. Review 2026-09-12, findings #1, #2, #12.
karthik1729
added a commit
that referenced
this pull request
Sep 12, 2026
…lk has a ceiling
The `.git` guard knew five HFS-ignorable code points where git's own table has sixteen, so
`.g\u{200e}it` reached a checkout as `.git`; it compared `.`/`..` before trimming the trailing
dots and spaces NTFS drops, so `".. "` was the parent directory there; and it let `:` through,
which opens an alternate data stream (`.git::$DATA`). The table is git's, the trim comes first,
and `:` is refused.
A commit diff recursed once per tree level with no bound under `panic = "abort"`, and its 4 MiB
cap applied only while formatting, after every changed path was already in memory. The walk
stops at 512 levels with an error and at 20 000 paths with the truncation marker.
A fetch naming a `want` that was neither a tip nor a commit, or a `deepen-not` that was not an
ancestor, walked the whole history with nothing counting it. The commit walks carry a budget of
two million commits, the shallow walk is interruptible and counted like the others, a fetch may
name at most 64 wants that are not tips before the whole-repository closure is refused, and
`deepen-since` reads each parent's time once.
Review findings #2, #3, #120, #122, and the walk memo.
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.
Bumps actions/cache from 4.3.0 to 6.1.0.
Release notes
Sourced from actions/cache's releases.
... (truncated)
Changelog
Sourced from actions/cache'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 issues