Bump j178/prek-action from 1 to 2 in the all-actions group#367
Conversation
Bumps the all-actions group with 1 update: [j178/prek-action](https://github.com/j178/prek-action). Updates `j178/prek-action` from 1 to 2 - [Release notes](https://github.com/j178/prek-action/releases) - [Commits](j178/prek-action@v1...v2) --- updated-dependencies: - dependency-name: j178/prek-action dependency-version: '2' dependency-type: direct:production update-type: version-update:semver-major dependency-group: all-actions ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d5cee3ed96
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
|
|
||
| - name: Run prek | ||
| uses: j178/prek-action@v1 | ||
| uses: j178/prek-action@v2 |
There was a problem hiding this comment.
Avoid tracking the prek action's beta v2 line
In .github/workflows/ci.yml, this swaps the prek job from j178/prek-action@v1 (whose latest release is the stable v1.1.1) to @v2, but upstream still marks the entire v2.0.0-beta.* series as Pre-release and documents v2 as a moving tag. That means our CI lint job will start following prerelease behavior, so unrelated PRs can begin failing whenever the action’s beta tag moves again. If we want to trial v2, it would be safer to pin an explicit beta tag/SHA or wait for a stable v2 release.
Useful? React with 👍 / 👎.
Bumps the all-actions group with 1 update: j178/prek-action.
Updates
j178/prek-actionfrom 1 to 2Release notes
Sourced from j178/prek-action's releases.
... (truncated)
Commits
7ae2ccbUseprek-actioin@v2in README7ebcc43Update prek version manifest for prek 0.3.6 (#98)0ea2253Improve manifest update PR details (#97)93b7a40Optimize Windows zip extraction (#96)1242fd6Improve version resolution fast paths (#94)f0e45c5Simplify manifest version handling (#92)c129827Clarify moving tag examples in README (#93)f90cb0afix: skip cache save on exact primary key hit (#91)66f7badci(release): float minor tags and restrict to default branch (#90)4e7ea35chore: remove zizmor github-env exception for action.yaml (#89)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 <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions