chore(deps): refresh workspace toolchain and package versions - #20
Merged
Conversation
Update the workspace catalog for ESLint and jsdom, then align app and package manifests with the newer Next.js, Prisma, React, Tailwind, and utility releases reflected in the lockfile.
Keep the outline walk generic so the ingestion service can accept the parser output without narrowing the element type first.
Keep the workspace metadata consistent with the rest of the YAML style.
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.
Refresh the shared toolchain and lockfile so the workspace stays aligned on
current Nest, Next, React, Prisma, Turbo, and TypeScript releases.
This also centralizes shared lint/runtime versions in pnpm catalogs. ESLint
stays on 9.x until the plugin stack supports 10, and jsdom remains pinned to
26.1.0 for Jest compatibility.