Realign the fork so it diffs from upstream actions/cache only by the GCS
cache backend, instead of carrying unrelated downgrades and deletions.
- Restore package.json/package-lock.json to upstream 5.0.4 deps; the fork
had downgraded to 4.2.x. Re-add @google-cloud/storage (gcsCache.ts needs it).
- Rebuild dist/ against the restored deps so it bundles the real GCS client
rather than a stale build against downgraded deps.
- Restore deleted upstream files: 7 workflow YAMLs, .github/CODEOWNERS,
.licensed.yml. (To be disabled in the fork, not removed.)
- Revert action.yml/restore/save manifests to upstream name/description/
author; keep only the gcs-bucket/gcs-path-prefix inputs as the fork diff.
- auto-tag.yml: track upstream's highest semver release tag, moving both the
exact-version tag and the major alias, instead of force-pinning v1.
- Remove checkout/ composite action; relocated to Cula-Technologies/checkout.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Drop workflows we don't need on the fork:
- licensed.yml (no .licenses for @google-cloud/storage)
- workflow.yml (jest tests mock @actions/cache, break with wrapper)
- close-inactive-issues, issue-opened, pr-opened (upstream oncall)
- publish-immutable-actions (not publishing to marketplace)
- release-new-action-version (replaced by auto-tag.yml)
Drop CODEOWNERS so merges don't require @actions/actions-cache review.
Drop .licensed.yml config (no longer used).
This workflow file publishes new action releases to the immutable action package of the same name as this repo.
This is part of the Immutable Actions project which is not yet fully released to the public. First party actions like this one are part of our initial testing of this feature.