Bump j178/prek-action from 2.0.4 to 2.0.6 - #231
Conversation
dependabot
Bot
added
dependencies
🔵 Review postedLast updated: 2026-08-01 00:18 UTC |
rtibblesbot
left a comment
rtibblesbot
left a comment
There was a problem hiding this comment.
PR #231 — dependency update review.
Package: j178/prek-action v2.0.4 → v2.0.6 (GitHub Actions)
Semver risk: patch
Type: development / CI-only — used once, by the linting job in .github/workflows/pre-commit.yml:32. No runtime or packaging impact.
- Breaking changes: none. No inputs or outputs added, removed, or renamed; this repo passes no
with:block, so there is no input surface to break. - Security fixes: none referenced.
- Peer/transitive changes: none re-exported. The
@actions/cacheandsemverbumps in the compare view are internal to the action. - Functional: musl Linux target support (unused — runner is
ubuntu-latest); color disabled inprek cache diroutput (bugfix for ANSI codes leaking into the parsed path); known-version manifest entries for prek 0.4.6–0.4.10.
No code changes required.
CI: failing — but not because of this bump. The Linting check fails on the Regenerate files hook (rebuild-from-specs, entry: make build), which leaves js/package.json dirty with 0.2.18 → 0.2.19. Cause is setuptools-scm version derivation, not the action: tag v0.2.18 sits on main's HEAD, so any branch one or more commits past it resolves to 0.2.19.devN+..., which pep440_to_npm_semver truncates to 0.2.19. Confirmed against a control — PR #230 still runs prek-action@v2.0.4 at the same commit base and fails the identical hook. Every other hook passes here.
Nothing to change in this PR; the codegen/versioning issue should be tracked separately (it will block every PR until the next release tag lands). Not approving only because Linting is red — if it is a required check it will gate the merge button regardless of cause.
One note for the record: the action's prek-version input defaults to latest, so this bump does not change which prek binary CI runs (both v2.0.6 here and v2.0.4 on #230 installed prek 0.4.11, while uv.lock pins 0.4.5 locally). Out of scope here.
@rtibblesbot's comments are generated by an LLM, and should be evaluated accordingly
How was this generated?
Ran a dependency-update review pipeline over the version bump:
- Classified the bump by semver (patch / minor / major) and dependency type (production vs. development)
- Extracted the changelog and release notes across the version range
- Assessed compatibility with this project's usage and whether any code changes are required
- Treated CI as the primary safety net
- Scaled the review depth to the update's risk
- Chose the verdict from semver risk, changelog findings, and CI status
|
@dependabot rebase |
Bumps [j178/prek-action](https://github.com/j178/prek-action) from 2.0.4 to 2.0.6. - [Release notes](https://github.com/j178/prek-action/releases) - [Commits](j178/prek-action@v2.0.4...v2.0.6) --- updated-dependencies: - dependency-name: j178/prek-action dependency-version: 2.0.6 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
d76983e to
513c6f1
Compare
2 participants
Bumps j178/prek-action from 2.0.4 to 2.0.6.
Release notes
Sourced from j178/prek-action's releases.
Commits
5337cb9Disable color inprek cache diroutput (#168)6368183Update known versions for prek 0.4.10 (#167)c4fa771Update pre-commit hook biomejs/pre-commit to v2.5.1 (#164)99728f0Update zizmorcore/zizmor-action action to v0.5.7 (#165)55aa53fUpdate actions/checkout action to v7 (#166)e191cc3Update dependency semver to v7.8.5 (#147)6017a0fUpdate dependency@actions/cacheto v6.1.0 (#148)5b6c2d6Update npm dev dependencies (#151)6757ec2Update known versions for prek 0.4.9 (#163)1cd265eUpdate known versions for prek 0.4.8 (#162)