Use RunsOn repository cache prefix - #58
Merged
Merged
Conversation
crohr
force-pushed
the
shared-prefix
branch
2 times, most recently
from
June 14, 2026 20:33
53a25d5 to
1de0d50
Compare
crohr
changed the title
maxvandongenTikkie
added a commit
to TikkieOrg/cache
that referenced
this pull request
Aug 28, 2026
* update to node24 * update licences * license and compiled * Approve license * Update cache to use local cache package and Node 24 support - Use local cache package with file:../packages/cache instead of published version - Update all action.yml files to use node24 runtime - Update dependencies to support Node 24 (@types/node@24.1.0) - Rebuild dist files with local cache package - Add engines field requiring node >=24 * Build dist files for Node 24 * chore: rebuild dist with local @actions/cache (core v2, exec v2) * chore: use local @actions/core, exec, io packages * Build with @actions/cache v5.0.0 * Use published @actions/core, exec, io v2.0.0 * chore: rebuild with @actions/cache v5.0.0 Uses updated cache package that removes @azure/ms-rest-js dependency to fix Node 24 punycode deprecation warning. * Update with core 2.0.1 which has exec 2.0.0 * chore: update @actions/core to 2.0.1 * Latest dist with core changes * Extra dist change * chore: use published @actions/cache v5.0.0 * chore: update license cache for @actions/cache v5.0.0 * chore: rebuild dist with @actions/cache v5.0.0 * chore: update actions/checkout to v5 in workflow files * chore: bump version to 5.0.0 for Node.js 24 support * docs: update README with v5 release notes * Revert "docs: update README with v5 release notes" This reverts commit fe92eaf. * chore: revert README to main branch state * chore: set version to 4.3.0 for prepare release PR * chore: rebuild dist with version 4.3.0 * chore: regenerate package-lock.json * undo readme changes * Prepare v5.0.0 release - Bump package version to 5.0.0 - Add v5.0.0 release notes (Node.js 24 runtime + runner requirement) * docs: update README for v5 release with Node 24 and runner version requirements * readme note * docs: highlight v5 runner requirement in releases * fix: update @actions/cache with storage-blob fix for Node.js 24 punycode deprecation * peer * fix: update @actions/cache to ^5.0.1 for Node.js 24 punycode fix Updates @actions/cache to version 5.0.1 which includes the @azure/storage-blob update that fixes the punycode deprecation warning on Node.js 24. * fix: update license files for @actions/cache, fast-xml-parser, and strnum * fix: add peer property to package-lock.json for dependencies * chore: release v5.0.1 - Bump version to 5.0.1 - Fix Node.js 24 punycode deprecation warning via @actions/cache@5.0.1 - Updates @azure/storage-blob to ^12.29.1 Related: actions#1685 * docs: Update examples to cache@v5 * docs: Update other actions in examples to the latest version * Bump actions/cache to 5.0.3 * Add PR link to releases * Build * Update licensed record for cache * license for httpclient * Add 5.0.3 builds * Upgrade dependencies and address security warnings - Bump `@actions/cache` to v5.0.5 - Bump `@actions/core` to v2.0.3 * Add licensed output * Add review for the @actions/http-client license * Update contribution docs * Add note * Potential fix for code scanning alert no. 52: Workflow does not contain permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com> * Fix permissions for workflows/workflow.yml * Fix workflow permissions and cleanup * Cleanup workflow file names * Update .github/workflows/pr-opened-workflow.yml Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Rewrite and simplify * Add wait for proxy * Fix resolution * Add traffic sanity check step * Fix cache key in examples.md for bun.lock Updated cache key to use 'bun.lock' instead of 'bun.lockb' for consistency. * Update dependencies & patch security vulnerabilities * Add licenses * Update RELEASES * Update ts-http-runtime to 0.3.5 * npm run build generated dist files * licensed changes * Ship v5 cache branch * Fix workflow * Update cache dependencies and release workflow * Fix audit finding and disable npm scripts * Use RunsOn repository cache prefix (runs-on#58) * Use RunsOn shared cache prefix for S3 backend * Use RunsOn repo cache prefix for S3 backend * Add custom tar implementation with multithreaded zstd decompression Replace upstream unzstd (single-threaded) with zstd -d -T0 for extraction and zstd -T0 for compression, using all available CPU cores. Accepts a configurable compression level to support --fast=N. Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai> * Wire compression-level input through restore and save Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai> * Expose compression-level input in action manifests Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai> * fix: correct zstd --long window and compression-level semantics - Change --long=30 → --long=29 in compress and decompress --long=30 allocates a 1 GB decompression buffer; on 3 GB runners this is a third of total RAM. --long=29 (512 MB window) gives identical compression ratio with half the memory cost. - Fix compression-level semantics: positive values now correctly map to zstd -N (quality level) instead of --fast=N (was inverted). Negative values map to --fast=|N|. Extracted buildLevelFlag() helper with inline documentation. - Update action.yml description for compression-level input - Rebuild dist/ * chore: align Tikkie cache with upstream v5 * docs: publish upstream v5 as TikkieOrg v6 * fix: resolve code scanning findings * ci: verify pull requests on hosted runners * test: preserve stdout write contract * test: reset expected action failures --------- Co-authored-by: Salman Chishti <salmanmkc@GitHub.com> Co-authored-by: XZTDean <xztdean@gmail.com> Co-authored-by: Ryan Ghadimi <ghadimir@github.com> Co-authored-by: Ryan Ghadimi <114221941+GhadimiR@users.noreply.github.com> Co-authored-by: Bassem Dghaidi <568794+Link-@users.noreply.github.com> Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: Ryan Peck <1244954+RyPeck@users.noreply.github.com> Co-authored-by: Yang Cao <yacaovsnc@github.com> Co-authored-by: Cyril Rohr <hey@cyrilrohr.com> Co-authored-by: thijsdegroot <thijs.de.groot@nl.abnamro.com> Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
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
1 participant
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.
User-facing changes
RUNS_ON_S3_CACHE_REPO_PREFIXwhen RunsOn provides it, storing v5 caches undercache/repo/<owner>/<repo>/....cache/<owner>/<repo>/...as the fallback outside RunsOn or when the variable is absent.Reviewer notes