build(deps): bump the npm_and_yarn group across 1 directory with 2 updates - #1
Closed
dependabot[bot] wants to merge 8 commits into
Closed
build(deps): bump the npm_and_yarn group across 1 directory with 2 updates#1dependabot[bot] wants to merge 8 commits into
dependabot[bot] wants to merge 8 commits into
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Runs on every push and pull request. The secret scan goes first so a leaked credential can never reach a build log, then lint, type-check, the 94 unit tests, and a production build. A second job boots the built server and asserts all ten routes return 200. The light-mode contrast, hydration and encoding bugs fixed in 6404b71 would each have been caught by this before reaching main.
The unit tests import their subjects with explicit .ts extensions, which node --test resolves but tsc rejected as TS5097. next build never surfaced it because it only type-checks the app graph, so the error sat unnoticed until CI ran tsc across the whole project. noEmit is already true, so allowImportingTsExtensions is permitted and keeps the tests inside the type-check rather than excluding them.
npm test uses node --test --experimental-strip-types, which only exists from Node 22.6. On Node 20 the flag is unrecognised and the step failed instantly with exit code 1. The app itself still runs on Node 20 (package.json engines); only the TypeScript test runner needs 22.
The repository already had 94 passing unit tests in src/lib/*.test.ts with no way to run them from npm, so nothing in CI or a contributor's workflow ever invoked them. Requires Node 22.6+ for --experimental-strip-types; the app itself still runs on Node 20.
…dates Bumps the npm_and_yarn group with 2 updates in the / directory: [next](https://github.com/vercel/next.js) and [postcss](https://github.com/postcss/postcss). Updates `next` from 15.5.2 to 15.5.21 - [Release notes](https://github.com/vercel/next.js/releases) - [Commits](vercel/next.js@v15.5.2...v15.5.21) Updates `postcss` from 8.4.31 to 8.5.23 - [Release notes](https://github.com/postcss/postcss/releases) - [Changelog](https://github.com/postcss/postcss/blob/main/CHANGELOG.md) - [Commits](postcss/postcss@8.4.31...8.5.23) --- updated-dependencies: - dependency-name: next dependency-version: 16.3.2 dependency-type: direct:production - dependency-name: postcss dependency-version: 8.5.23 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/multi-601b3063ac
branch
from
August 23, 2026 18:25
43e8454 to
f7a6aaa
Compare
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
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
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.
Bumps the npm_and_yarn group with 2 updates in the / directory: next and postcss.
Updates
nextfrom 15.5.2 to 15.5.21Release notes
Sourced from next's releases.
Commits
e26f6ffv15.5.217f5deeb[15.x] Improve performance of checking valid MPA form submissions57c31f7[15.x] EnforceserverActions.bodySizeLimitfor Server Actions in Edge runtimee3e5666[15.x] Set correct origin for internal redirects in custom server35f5013[15.x] Ensure exotic rewrite param values are properly encoded062f667[15.x] fix(fetch-cache): key fetch(Request, init) by the effective request577c9dc[15.x] fix(incremental-cache): byte-exact fetch cache key for binary bodies530d4fa[15.x] fix(next/image): improve performance of detectContentType()8fabaf3[15.x] Performance improvements when decoding React Server function payloadsff12a61[15.x] Validate server reference IDs during manifest lookupMaintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for next since your current version.
Updates
postcssfrom 8.4.31 to 8.5.23Release notes
Sourced from postcss's releases.
... (truncated)
Changelog
Sourced from postcss's changelog.
... (truncated)
Commits
eb9e1feRelease 8.5.23 version9d19c78Update dependencies7beca13Does no load source map file without opts.fromdecea51Typoc18e30dUpdate EM banner98a39adUpdate EM bannera3e48c4Release 8.5.22 versionf49d691Fix custom property losing its semicolon before a comment (#2117)28e0dafRelease 8.5.21 version3d2b4e4Update dependenciesMaintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for postcss since your current version.