chore(deps): adopt @nest-native/jobs 0.2.1 and messaging 0.5.1 - #74
Merged
Conversation
Both releases widened their better-sqlite3 peer range to ^11 || ^12 || ^13. The jobs bump crosses a 0.x minor, so the old "^0.1.0" range could never pick it up — which is why #69 (better-sqlite3 13) kept failing to install with ERESOLVE even after the libraries shipped. messaging's "^0.5.0" already covered 0.5.1; pinned explicitly for clarity. No application code changes: the app only reads tick() results, never constructs a TickReport, so jobs 0.2.0's added `scheduled` field is not a break here. Cron schedules stay opt-in and are not adopted in this change. Verified locally: typecheck, lint, complexity, build, audit, and the full suite (86 passing, unchanged from main).
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.
Unblocks #69.
Both libraries just shipped an isolated better-sqlite3 major review (jobs#16 → 0.2.1, messaging#32 → 0.5.1) widening their peer range to
^11 || ^12 || ^13.That alone was not enough here:
@nest-native/jobswas pinned at^0.1.0, and for 0.x releases caret does not cross a minor — so npm kept resolving jobs@0.1.0 with its old^11 || ^12peer and #69 kept failing withERESOLVE. Verified with a dry-run probe:^0.1.0+ better-sqlite3 13 still errors,^0.2.1+ better-sqlite3 13 resolves clean.messaging's
^0.5.0already covered 0.5.1; pinned explicitly so the intent is visible.No application code changes. The app only reads
tick()results and never constructs aTickReport, so thescheduledfield added in jobs 0.2.0 is not a break here. Cron schedules remain opt-in and are not adopted in this PR.Verified locally (after
npm rebuild better-sqlite3— npm's allow-scripts policy leaves the native binary unbuilt): typecheck, lint, complexity, build, security:audit all clean, and the full suite passes 86/86, identical to main.