Update dependencies - #89
Merged
Merged
Conversation
Bump Next.js, ESLint, typescript-eslint, and @types/node to latest patch/minor releases, and refresh transitive packages. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
2 participants
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.
Routine dependency refresh. All packages are now at their latest published versions (
yarn outdatedreports nothing).Changes
Direct bumps in
package.json:@typescript-eslint/eslint-plugin@typescript-eslint/parserPicked up within existing semver ranges (lockfile only):
nexteslint-config-next@next/eslint-plugin-nexteslint@types/nodePlus a refresh of transitive packages. All updates are patch/minor — no major version changes.
Verification
yarn build— passes, TypeScript clean, all 15 routes generated.yarn test— green in CI: all 40 tests pass, visual regressions included. Theupdate-snapshotsjob was skipped, so no baselines needed changing.Note on running the visual tests locally
The 6
toHaveScreenshottests fail in the sandbox I developed this in, because it only has Chromium v1194 available while the committed snapshots were generated with the v1234 that Playwright 1.62 pins. The two render text with slightly different metrics.I confirmed this was environmental rather than a regression by re-running the visual tests against the pre-update dependencies with the same browser: they failed identically, down to the exact differing-pixel counts (
637411and294781). CI, which installs the pinned Chromium, passes them — as it did here.Worth flagging only so nobody is tempted to run
yarn test:update-snapshotsin a similar environment: that would overwrite good baselines with screenshots taken by the wrong browser.