Repository navigation
Releases: emosheeep/lockfile-conflicts
Releases · emosheeep/lockfile-conflicts
Release list
v0.5.2
Patch Changes
- Improve interrupted
runAfterreporting so Ctrl+C displays asinterruptedinstead ofexit code 130. - Stop lingering
runAfterprocess groups after Ctrl+C so command output does not continue after Git rebase completes.
v0.5.1
Patch Changes
- Repair packaged foreground helper executable permissions at runtime, falling back to direct
runAfterexecution if the helper cannot be made executable.
v0.5.0
Minor Changes
- Add a native foreground helper so Ctrl+C during
runAfterdoes not interrupt an in-progress Git rebase. - Make hook cleanup resilient when
runAfteror lockfile hook execution fails, avoiding stale Git rebase state. - Package foreground helper binaries for common Linux and macOS targets and fall back to the previous direct execution path when no helper is available.
- Add a timestamped test-publish workflow for alpha/beta/next prereleases.
- Simplify generated hook injection so it only prepends the local bin directory to find
lockfile; runAfter keeps using the user's normal environment.
v0.4.0
Minor Changes
- 7f97c67: Guard generated Git hooks before running
lockfile cleanup, avoid mutating global hooks while supporting hook-manager shim directories and shared worktree hooks, and migrate the project toolchain to pnpm 11, Oxlint, and Oxfmt.
v0.3.0
Minor Changes
- feat: use inherit stdio to print command log instead of spinner
v0.2.1
Patch Changes
- 0c2ec1e: feat: just hook stage in cleanup to avoid mis executing.
chore: use local installed package first.