restore-jupyter-cache: cache freshness warning and cache-age-days output
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 0
- Forks
- 1
- Avg merge
- 32m
- Merged PRs (30d)
- 3
Description
#92 Phase 2: cache freshness warning in restore-jupyter-cache, so a stale cache is loud instead of silent (the #83 failure mode: 40-minute cold builds on every PR for ~2 months).
- Write
.cache-metadata.jsonat save time - Age check on restore:
::warning::+ step-summary when the cache is older than expected - New
cache-age-daysoutput
Not started — the action declares exactly two outputs, cache-hit and cache-key (restore-jupyter-cache/action.yml:39-45), and no cache-metadata/cache-age string exists in the repo. No consumer repin needed on release: all 11 call sites float on @v0.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with restore-jupyter-cache/action.yml:39-45 to confirm the current outputs, then trace the action's save and restore entry points. Done means cache metadata is written at save time, stale restores emit a warning and step summary, and the action exposes the cache-age-days output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, shell
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100