| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
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>
🟡 Waiting for changesLast updated: 2026-09-01 00:12 UTC |
Sorry, something went wrong.
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.
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:
Sorry, something went wrong.
| enable-cache: true | ||
| cache-python: true | ||
| - uses: j178/prek-action@v2.0.6 | ||
| - uses: j178/prek-action@v3.0.0 |
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.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Bumps j178/prek-action from 2.0.6 to 3.0.0.
Release notesSourced from j178/prek-action's releases.
CommitsDependabot 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: