Bump j178/prek-action from 2.0.6 to 3.0.0 - #235
Open
dependabot[bot] wants to merge 1 commit into
Open
Conversation
Bumps [j178/prek-action](https://github.com/j178/prek-action) from 2.0.6 to 3.0.0. - [Release notes](https://github.com/j178/prek-action/releases) - [Commits](j178/prek-action@v2.0.6...v3.0.0) --- updated-dependencies: - dependency-name: j178/prek-action dependency-version: 3.0.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Contributor
🟡 Waiting for changesLast updated: 2026-09-01 00:12 UTC |
rtibblesbot
reviewed
Sep 1, 2026
rtibblesbot
left a comment
rtibblesbot
left a comment
Contributor
There was a problem hiding this comment.
PR #235 — j178/prek-action 2.0.6 → 3.0.0, major bump, CI-only (lint workflow, no runtime impact). CI passing, including All file linting, which runs the new action.
- Breaking change (not applicable): v3 stops publishing moving
@v3/@v3.0tags (#170). This repo pins the exact tag, andgrep -rn prek-action .github/finds no other reference. - Security fixes / deprecations / peer deps: none.
- Behavioral change: cache-key hashing fixed (#153) —
hashConfigFilesnow digests each config file's SHA-256 rather than streaming raw bytes. First run onmainafter merge is a cache miss, then self-heals. - Known checksums updated for prek 0.4.11, matching the pin from #232.
- No code changes required; the action is invoked with no inputs.
One nitpick inline about SHA pinning.
@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
| enable-cache: true | ||
| cache-python: true | ||
| - uses: j178/prek-action@v2.0.6 | ||
| - uses: j178/prek-action@v3.0.0 |
Contributor
There was a problem hiding this comment.
nitpick: The v3.0.0 notes recommend pinning the commit SHA now that tags are immutable:
- uses: j178/prek-action@4e14d07f9231acabce116ccfca13b13dd9755ece # v3.0.0Dependabot maintains SHA pins and their trailing version comments the same way it maintains tags. Better as a separate repo-wide pass than inside a Dependabot PR — an exact release tag is already a reasonable stopping point.
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.
Bumps j178/prek-action from 2.0.6 to 3.0.0.
Release notes
Sourced from j178/prek-action's releases.
Commits
4e14d07Drop floating version tag support (#170)d8e544eFix cache key hashing (#153)cd7e67cUpdate known versions for prek 0.4.11 (#169)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)