Bump prek from 0.3.8 to 0.3.10#218
Conversation
Bumps [prek](https://github.com/j178/prek) from 0.3.8 to 0.3.10. - [Release notes](https://github.com/j178/prek/releases) - [Changelog](https://github.com/j178/prek/blob/master/CHANGELOG.md) - [Commits](j178/prek@v0.3.8...v0.3.10) --- updated-dependencies: - dependency-name: prek dependency-version: 0.3.10 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
rtibblesbot
left a comment
There was a problem hiding this comment.
Routine patch update; safe to merge.
CI: Python unit tests all passing. Linting check failed due to rebuild-from-specs modifying js/package.json (version 0.2.17 → 0.2.18) — pre-existing mismatch unrelated to this bump.
Dependency Update Review
Package: prek 0.3.8 → 0.3.10 (spans two patch releases, 0.3.9 + 0.3.10)
Semver risk: Patch
Dependency type: Dev (listed under [dependency-groups] dev in pyproject.toml; not a production runtime dependency)
CI status: Tests passing; lint failing for an unrelated pre-existing reason (see above)
Changelog Analysis
Sources consulted:
- PR body (includes release notes and changelog for 0.3.9 and 0.3.10)
Breaking changes: None found in either release.
Other notable changes:
- 0.3.10: Improve merge conflict marker detection, hide up-to-date output in non-verbose mode, preserve frozen comment spacing in
auto-update, prefer stable Rust toolchains (bug fix) - 0.3.9:
prek auto-updatestricter about pinned revisions; can detect impostor commits;--checkflag can fail on frozen-ref mismatches
Compatibility Assessment
- Project uses
prekonly as a pre-commit hook runner (dev tooling); no prek API surface is called from application code - No peer dependency changes
- No code changes required
uv.lockalso updatesexclude-newerfrom a pinned timestamp to0001-01-01T00:00:00Zwith a backwards-compatibility comment; this is driven byexclude-newer-span = "P7D"inpyproject.tomland is expected lockfile behavior
Recommendation
APPROVE — patch bump of a dev-only tool, no breaking changes, all tests green.
@rtibblesbot's comments are generated by an LLM, and should be evaluated accordingly
How was this generated?
Reviewed the pull request diff checking for:
- Correctness: bugs, edge cases, undocumented behavior, resource leaks, hardcoded values
- Design: unnecessary complexity, naming, readability, comment accuracy, redundant state
- Architecture: duplicated concerns, minimal interfaces, composition over inheritance
- Testing: behavior-based assertions, mocks only at hard boundaries, accurate coverage
- Completeness: missing dependencies, unupdated usages, i18n, accessibility, security
- Principles: DRY (same reason to change), SRP, Rule of Three (no premature abstraction)
- Checked CI status and linked issue acceptance criteria
- For UI changes: inspected screenshots for layout, visual completeness, and consistency
Bumps prek from 0.3.8 to 0.3.10.
Release notes
Sourced from prek's releases.
... (truncated)
Changelog
Sourced from prek's changelog.
... (truncated)
Commits
1981c51Bump version to 0.3.10ba745f6Prefer stable Rust toolchains (#1974)b6c591dReimplement@j178/preknpm package (#1973)fba1c85Keep finished hooks visible (#1967)bce57a3Disallow rev for non-remote repos in schema (#1964)afac10cSplitauto_update.rsinto modules (#1962)c3b9f11Update GitHub Actions (major) (#1961)6ca0443Update Rust crate annotate-snippets to v0.12.15 (#1955)776277eUpdate Rust crate tokio to v1.51.1 (#1957)c2b445aUpdate Rust crate toml_edit to v0.25.11 (#1958)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)