Conversation
New versions will be published on `prek` releases, this job is no longer needed.
There was a problem hiding this comment.
Pull request overview
Removes the scheduled GitHub Actions workflow that automatically refreshes this action’s prek version metadata and opens PRs with updated manifest/checksum/bundled outputs.
Changes:
- Deletes the
Update Known Versionsworkflow that periodically rannpm run update-known-versionsand created PRs for updatedversion-manifest.json,src/known-checksums.ts, anddist/bundles.
Comments suppressed due to low confidence (1)
.github/workflows/update-known-versions.yml:1
- Deleting this workflow removes the only automated mechanism in this repo that refreshes
version-manifest.jsonandsrc/known-checksums.tsfrom upstreamj178/prekreleases. The runtime code uses the manifest to resolvelatestand semver ranges (and skips checksum verification when checksums are missing), so if these files aren’t updated elsewhere the action will lag behind new prek releases and may stop verifying new binaries. Consider adding an equivalent update step to the release workflow (or another automation) or changing runtime resolution to query releases directly solatest/ranges stay current.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2a97ae550a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| name: Update Known Versions | ||
|
|
||
| on: | ||
| schedule: | ||
| - cron: '17 3 * * *' |
There was a problem hiding this comment.
Keep a workflow that refreshes known prek versions
Removing this workflow leaves the repository with no in-repo automation that runs npm run update-known-versions (checked remaining workflow files: ci.yml, release.yml, zizmor.yml), so version-manifest.json/src/known-checksums.ts will stop tracking new prek releases unless someone updates them manually elsewhere. That breaks the action’s documented default behavior over time because latest and semver ranges are resolved from the manifest (src/manifest.ts), and newer exact versions lose checksum verification when their entries are missing (src/install.ts).
Useful? React with 👍 / 👎.
New versions will be published on
prekreleases, this job is no longer needed.