release: v1.6.1#148
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #148 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 37 37
Lines 1089 1089
Branches 222 221 -1
=========================================
Hits 1089 1089 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the version of @jaredwray/mockhttp from 1.6.0 to 1.6.1 in package.json. The reviewer suggests that this change should be a minor version bump to 1.7.0 instead of a patch release, as narrowing Node.js engine requirements constitutes a breaking change under Semantic Versioning.
| { | ||
| "name": "@jaredwray/mockhttp", | ||
| "version": "1.6.0", | ||
| "version": "1.6.1", |
There was a problem hiding this comment.
Narrowing the engines.node requirement from >=22.13.0 to >=22.18.0 (as noted in the release summary) is technically a breaking change for users running on the now-excluded versions of Node.js. According to Semantic Versioning, this should be a minor version bump (e.g., 1.7.0) rather than a patch release (1.6.1).
| "version": "1.6.1", | |
| "version": "1.7.0", |
References
- When upgrading dependencies, ensure the project's
enginesfield inpackage.jsonis updated to align with any stricter Node.js version requirements. Narrowing these requirements is a breaking change that necessitates a minor or major version bump according to Semantic Versioning.
2 participants
Release summary
Routine maintenance: dependency refresh (fastify, @scalar/api-reference, hookified), pnpm 11 supply-chain baseline, and GitHub Actions major upgrades.
@jaredwray/mockhttp@1.6.1 — 2026-05-18
Routine maintenance: dependency refresh (fastify, @scalar/api-reference, hookified), pnpm 11 supply-chain baseline, and GitHub Actions major upgrades.
Internal
e431858, root - chore: upgrade hookified #147)e07afea, root - chore: upgrade @scalar/api-reference #146)bcfddf6, root - chore: upgrade fastify dependencies #145)a47cf91, root - chore: upgrade GitHub Actions (breaking) #144)5ab1512, root - chore: upgrade TypeScript and build tooling #143)5cef6c7, root - chore: upgrade TypeScript and build tooling #143)edfdf90, root - chore: upgrade code quality dependencies #142)8bf7cd1, chore: upgrade to pnpm 11 via corepack with defense-in-depth workspace #141)ca65ce5, chore: upgrade to pnpm 11 via corepack with defense-in-depth workspace #141)1d93b64, chore: upgrade to pnpm 11 via corepack with defense-in-depth workspace #141)Contributors
Full List of Changes
Full diff: v1.6.0...v1.6.1
Verification
pnpm install --frozen-lockfilesucceedspnpm buildsucceeds (tsdown 0.22.0, target node22.18.0)pnpm test:cipasses (413 tests, 100% line coverage)Post-merge
Merge then create a GitHub Release at tag
v1.6.1— therelease.yamlworkflow publishes to npm on therelease: releasedevent.Notes
v1.6.0arechore/ci(nofeat:/fix:); the shipping reason is the consumer-facing runtime dep bumps (fastify, @scalar/api-reference, hookified) plus the pnpm 11 / Actions baseline.engines.nodenarrowing from>=22.13.0→>=22.18.0(forced bytsdown 0.22.0) is treated as patch — it's a 5-minor tightening within the Node 22 line. Strict semver could argue for minor; please override at merge if preferred.(breaking)marker on root - chore: upgrade GitHub Actions (breaking) #144 is CI-internal (Actions major bumps), not a consumer break.Generated by Claude Code