fix(deps): update nextjs monorepo (16.3.0 → 16.3.1) - #767

Merged
joryirving merged 1 commit into
mainfrom
renovate/nextjs-monorepo
Aug 14, 2026
Merged

fix(deps): update nextjs monorepo (16.3.0 → 16.3.1)#767
joryirving merged 1 commit into
mainfrom
renovate/nextjs-monorepo

Conversation

@its-miso

@its-misoits-misoBot commented Aug 13, 2026•
edited
Loading

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

PackageChangeAgeAdoptionPassingConfidence
eslint-config-next (source)16.3.0 → 16.3.1ageadoptionpassingconfidence
next (source)16.3.0 → 16.3.1ageadoptionpassingconfidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

vercel/next.js (eslint-config-next)

v16.3.1

Compare Source

What's Changed

Full Changelog: vercel/next.js@v16.3.0...v16.3.1

Configuration

📅 Schedule: (in timezone America/Edmonton)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

@its-miso
its-misoBot requested a review from joryirving as a code ownerAugust 13, 2026 22:42
its-saffron[bot]

This comment was marked as outdated.

Sign in to view

@its-miso
its-misoBotforce-pushed the renovate/nextjs-monorepo branch from 1a53000 to 2f8ca61CompareAugust 13, 2026 23:41
@its-misoits-misoBot changed the title fix(deps): update dependency eslint-config-next (16.3.0 → 16.3.1)fix(deps): update nextjs monorepo (16.3.0 → 16.3.1)Aug 13, 2026
its-saffron[bot]
its-saffronBot approved these changes Aug 13, 2026
View reviewed changes

@its-saffronits-saffronBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AI Automated Review

Full PR review.

Analysis engine: dsv4f@https://litellm.jory.dev/v1 (openai) — primary route

Recommendation: Approve. This Renovate PR bumps the Next.js monorepo (next, eslint-config-next, @next/env, @next/eslint-plugin-next, the @next/swc-* platform binaries, and @swc/helpers) from 16.3.0 to 16.3.1, entirely within package-lock.json. No source, manifest, or Dockerfile changes. CI is green on the head commit, and the upstream 16.3.1 release is a patch-level set of backported fixes with no API or engine changes.

Change-by-change findings

  • package-lock.json — next 16.3.0 → 16.3.1 together with its matched dependencies: @next/env 16.3.1, @next/eslint-plugin-next 16.3.1, eslint-config-next 16.3.1, all eight @next/swc-* optional platform binaries at 16.3.1, and @swc/helpers 0.5.15 → 0.5.23 (bumped upstream in this same release). Every package moves in lockstep from a single published release, so there is no version skew between next and its native binaries on any target platform (linux musl/gnu, darwin, win32).
  • The PR title names only eslint-config-next, but the diff also updates the runtime next package and its dependencies; this is consistent with Renovate's nextjs-monorepo grouping and the lockfile is internally coherent.
  • Release evidence (Next.js v16.3.1, published 2026-08-13): all 22 commits are backported fixes on the 16.3 branch — Turbopack runtime/HMR and module-registration fixes, a next/image response-preservation fix, a styled-jsx Pages Router SSR fix, cache-tag/revalidation and unstable_cache naming fixes, a dev-validation worker fix, and a revert of an i18n localization change for dynamic Pages API routes. No public API changes, no peerDependency changes, and no breaking changes are listed; the installed lockfile metadata retains engines.node >= 20.9.0 unchanged.
  • The i18n revert applies to dynamic Pages Router API routes, while Dispatch uses the App Router (per AGENTS.md tech stack), so this revert is not expected to affect this application.
  • Host-platform coupling check: the Dockerfile pins the runtime to node:24-bookworm-slim and package.json declares engines.node >= 24; the installed next@16.3.1 declares node >= 20.9.0, so Node 24 is within the supported range. The lockfile engines field for the exact installed version is the binding constraint and it is satisfied.
  • Override coherence: next@16.3.1 still carries postcss 8.5.23 and optional sharp ^0.35.3, so the documented postcss/sharp override rationale in package.json remains accurate after this bump.

Standards Compliance

The change conforms to AGENTS.md: lockfile-only dependency update with no environment-variable, Prisma-schema, or Docker-base-image changes; the Docker npm ci stages consume the updated lockfile as-is; lint and typecheck gates still block CI and both passed.

Tool Harness Findings

CI on head commit 2f8ca61 reached a terminal success state for all checks: Build, Docker Build, Lint, Tests, Typecheck, and npm audit — all success. This directly satisfies the must-check "run full test suite after upgrade."

Unknowns or Needs Verification

  • The "check for breaking API changes" must-check is satisfied from the component's own release evidence: a patch release with backported fixes only, no API or engine changes. A separate Node.js compatibility-matrix fetch could not be completed within the tool budget, but the installed lockfile's node >= 20.9.0 engine declaration is the authoritative floor and Node 24 satisfies it.
  • No other unknowns: no image digest changes in the diff, no linked issues to compare against, and no evidence-provider findings were present in the corpus.

Sources

  • Next.js v16.3.1 release notes: https://github.com/vercel/next.js/releases/tag/v16.3.1
  • GitHub compare metadata for v16.3.0...v16.3.1 (22 commits, all backports)
  • Repository files read: Dockerfile (node:24-bookworm-slim), package.json (engines >=24, override rationale), and the updated package-lock.json entries.

@joryirving
joryirving merged commit 0aa4c84 into mainAug 14, 2026
7 checks passed
@joryirving
joryirving deleted the renovate/nextjs-monorepo branch August 14, 2026 00:22
@joryirvingjoryirving mentioned this pull request Aug 14, 2026
Merged
@its-saffronits-saffronBot mentioned this pull request Aug 19, 2026
Merged
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@its-saffronits-saffron[bot]its-saffron[bot] approved these changes
@joryirvingjoryirvingAwaiting requested review from joryirvingjoryirving is a code owner

Assignees

No one assigned

Labels

type/patch

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@joryirving
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all 
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '

Skip to content
fix(deps): update nextjs monorepo (16.3.0 → 16.3.1) - #767
Merged
joryirving merged 1 commit into
mainfrom 
renovate/nextjs-monorepo
Aug 14, 2026
Merged
fix(deps): update nextjs monorepo (16.3.0 → 16.3.1)#767
joryirving merged 1 commit into
mainfrom 
renovate/nextjs-monorepo
Conversation
@its-miso
@its-misoits-misoBot
commented
Aug 13, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
This PR contains the following updates:
PackageChangeAgeAdoptionPassingConfidence
eslint-config-next (source)16.3.0 → 16.3.1ageadoptionpassingconfidence
next (source)16.3.0 → 16.3.1ageadoptionpassingconfidence
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
vercel/next.js (eslint-config-next)
v16.3.1
Compare Source
What's Changed
Full Changelog: vercel/next.js@v16.3.0...v16.3.1
Configuration
📅 Schedule: (in timezone America/Edmonton)
  • Branch creation

    • At any time (no schedule defined)
  • Automerge

    • At any time (no schedule defined)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
  •  If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate CLI.
@its-miso
its-misoBot
requested a review
from joryirving
as a code ownerAugust 13, 2026 22:42
its-saffron[bot]

This comment was marked as outdated.

Sign in to view
@its-miso
its-misoBotforce-pushed
the
renovate/nextjs-monorepo
branch
from
1a53000 to
2f8ca61CompareAugust 13, 2026 23:41
@its-misoits-misoBot
changed the title
fix(deps): update dependency eslint-config-next (16.3.0 → 16.3.1)fix(deps): update nextjs monorepo (16.3.0 → 16.3.1)Aug 13, 2026
its-saffron[bot]
its-saffronBot
approved these changes
Aug 13, 2026
View reviewed changes
@its-saffronits-saffronBot
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AI Automated Review
Full PR review.
Analysis engine: dsv4f@https://litellm.jory.dev/v1 (openai) — primary route
Recommendation: Approve. This Renovate PR bumps the Next.js monorepo (next, eslint-config-next, @next/env, @next/eslint-plugin-next, the @next/swc-* platform binaries, and @swc/helpers) from 16.3.0 to 16.3.1, entirely within package-lock.json. No source, manifest, or Dockerfile changes. CI is green on the head commit, and the upstream 16.3.1 release is a patch-level set of backported fixes with no API or engine changes.
Change-by-change findings
  • package-lock.json — next 16.3.0 → 16.3.1 together with its matched dependencies: @next/env 16.3.1, @next/eslint-plugin-next 16.3.1, eslint-config-next 16.3.1, all eight @next/swc-* optional platform binaries at 16.3.1, and @swc/helpers 0.5.15 → 0.5.23 (bumped upstream in this same release). Every package moves in lockstep from a single published release, so there is no version skew between next and its native binaries on any target platform (linux musl/gnu, darwin, win32).
  • The PR title names only eslint-config-next, but the diff also updates the runtime next package and its dependencies; this is consistent with Renovate's nextjs-monorepo grouping and the lockfile is internally coherent.
  • Release evidence (Next.js v16.3.1, published 2026-08-13): all 22 commits are backported fixes on the 16.3 branch — Turbopack runtime/HMR and module-registration fixes, a next/image response-preservation fix, a styled-jsx Pages Router SSR fix, cache-tag/revalidation and unstable_cache naming fixes, a dev-validation worker fix, and a revert of an i18n localization change for dynamic Pages API routes. No public API changes, no peerDependency changes, and no breaking changes are listed; the installed lockfile metadata retains engines.node >= 20.9.0 unchanged.
  • The i18n revert applies to dynamic Pages Router API routes, while Dispatch uses the App Router (per AGENTS.md tech stack), so this revert is not expected to affect this application.
  • Host-platform coupling check: the Dockerfile pins the runtime to node:24-bookworm-slim and package.json declares engines.node >= 24; the installed next@16.3.1 declares node >= 20.9.0, so Node 24 is within the supported range. The lockfile engines field for the exact installed version is the binding constraint and it is satisfied.
  • Override coherence: next@16.3.1 still carries postcss 8.5.23 and optional sharp ^0.35.3, so the documented postcss/sharp override rationale in package.json remains accurate after this bump.
Standards Compliance
The change conforms to AGENTS.md: lockfile-only dependency update with no environment-variable, Prisma-schema, or Docker-base-image changes; the Docker npm ci stages consume the updated lockfile as-is; lint and typecheck gates still block CI and both passed.
Tool Harness Findings
CI on head commit 2f8ca61 reached a terminal success state for all checks: Build, Docker Build, Lint, Tests, Typecheck, and npm audit — all success. This directly satisfies the must-check "run full test suite after upgrade."
Unknowns or Needs Verification
  • The "check for breaking API changes" must-check is satisfied from the component's own release evidence: a patch release with backported fixes only, no API or engine changes. A separate Node.js compatibility-matrix fetch could not be completed within the tool budget, but the installed lockfile's node >= 20.9.0 engine declaration is the authoritative floor and Node 24 satisfies it.
  • No other unknowns: no image digest changes in the diff, no linked issues to compare against, and no evidence-provider findings were present in the corpus.
Sources
  • Next.js v16.3.1 release notes: https://github.com/vercel/next.js/releases/tag/v16.3.1
  • GitHub compare metadata for v16.3.0...v16.3.1 (22 commits, all backports)
  • Repository files read: Dockerfile (node:24-bookworm-slim), package.json (engines >=24, override rationale), and the updated package-lock.json entries.
@joryirving
joryirving
merged commit 0aa4c84
into
mainAug 14, 2026

7 checks passed

@joryirving
joryirving
deleted the

renovate/nextjs-monorepo

branch
August 14, 2026 00:22
@joryirvingjoryirving
mentioned this pull request
Aug 14, 2026
 Merged

@its-saffronits-saffronBot
mentioned this pull request
Aug 19, 2026
 Merged

Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@its-saffronits-saffron[bot]its-saffron[bot] approved these changes
@joryirvingjoryirvingAwaiting requested review from joryirvingjoryirving is a code owner

Assignees


No one assigned


Labels

type/patch

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

1 participant

@joryirving

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix");
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
fix(deps): update nextjs monorepo (16.3.0 → 16.3.1) - #767
Merged
joryirving merged 1 commit into
mainfrom 
renovate/nextjs-monorepo
Aug 14, 2026
Merged
fix(deps): update nextjs monorepo (16.3.0 → 16.3.1)#767
joryirving merged 1 commit into
mainfrom 
renovate/nextjs-monorepo
Conversation
@its-miso
@its-misoits-misoBot
commented
Aug 13, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
This PR contains the following updates:
PackageChangeAgeAdoptionPassingConfidence
eslint-config-next (source)16.3.0 → 16.3.1ageadoptionpassingconfidence
next (source)16.3.0 → 16.3.1ageadoptionpassingconfidence
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
vercel/next.js (eslint-config-next)
v16.3.1
Compare Source
What's Changed
Full Changelog: vercel/next.js@v16.3.0...v16.3.1
Configuration
📅 Schedule: (in timezone America/Edmonton)
  • Branch creation

    • At any time (no schedule defined)
  • Automerge

    • At any time (no schedule defined)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
  •  If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate CLI.
@its-miso
its-misoBot
requested a review
from joryirving
as a code ownerAugust 13, 2026 22:42
its-saffron[bot]

This comment was marked as outdated.

Sign in to view
@its-miso
its-misoBotforce-pushed
the
renovate/nextjs-monorepo
branch
from
1a53000 to
2f8ca61CompareAugust 13, 2026 23:41
@its-misoits-misoBot
changed the title
fix(deps): update dependency eslint-config-next (16.3.0 → 16.3.1)fix(deps): update nextjs monorepo (16.3.0 → 16.3.1)Aug 13, 2026
its-saffron[bot]
its-saffronBot
approved these changes
Aug 13, 2026
View reviewed changes
@its-saffronits-saffronBot
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AI Automated Review
Full PR review.
Analysis engine: dsv4f@https://litellm.jory.dev/v1 (openai) — primary route
Recommendation: Approve. This Renovate PR bumps the Next.js monorepo (next, eslint-config-next, @next/env, @next/eslint-plugin-next, the @next/swc-* platform binaries, and @swc/helpers) from 16.3.0 to 16.3.1, entirely within package-lock.json. No source, manifest, or Dockerfile changes. CI is green on the head commit, and the upstream 16.3.1 release is a patch-level set of backported fixes with no API or engine changes.
Change-by-change findings
  • package-lock.json — next 16.3.0 → 16.3.1 together with its matched dependencies: @next/env 16.3.1, @next/eslint-plugin-next 16.3.1, eslint-config-next 16.3.1, all eight @next/swc-* optional platform binaries at 16.3.1, and @swc/helpers 0.5.15 → 0.5.23 (bumped upstream in this same release). Every package moves in lockstep from a single published release, so there is no version skew between next and its native binaries on any target platform (linux musl/gnu, darwin, win32).
  • The PR title names only eslint-config-next, but the diff also updates the runtime next package and its dependencies; this is consistent with Renovate's nextjs-monorepo grouping and the lockfile is internally coherent.
  • Release evidence (Next.js v16.3.1, published 2026-08-13): all 22 commits are backported fixes on the 16.3 branch — Turbopack runtime/HMR and module-registration fixes, a next/image response-preservation fix, a styled-jsx Pages Router SSR fix, cache-tag/revalidation and unstable_cache naming fixes, a dev-validation worker fix, and a revert of an i18n localization change for dynamic Pages API routes. No public API changes, no peerDependency changes, and no breaking changes are listed; the installed lockfile metadata retains engines.node >= 20.9.0 unchanged.
  • The i18n revert applies to dynamic Pages Router API routes, while Dispatch uses the App Router (per AGENTS.md tech stack), so this revert is not expected to affect this application.
  • Host-platform coupling check: the Dockerfile pins the runtime to node:24-bookworm-slim and package.json declares engines.node >= 24; the installed next@16.3.1 declares node >= 20.9.0, so Node 24 is within the supported range. The lockfile engines field for the exact installed version is the binding constraint and it is satisfied.
  • Override coherence: next@16.3.1 still carries postcss 8.5.23 and optional sharp ^0.35.3, so the documented postcss/sharp override rationale in package.json remains accurate after this bump.
Standards Compliance
The change conforms to AGENTS.md: lockfile-only dependency update with no environment-variable, Prisma-schema, or Docker-base-image changes; the Docker npm ci stages consume the updated lockfile as-is; lint and typecheck gates still block CI and both passed.
Tool Harness Findings
CI on head commit 2f8ca61 reached a terminal success state for all checks: Build, Docker Build, Lint, Tests, Typecheck, and npm audit — all success. This directly satisfies the must-check "run full test suite after upgrade."
Unknowns or Needs Verification
  • The "check for breaking API changes" must-check is satisfied from the component's own release evidence: a patch release with backported fixes only, no API or engine changes. A separate Node.js compatibility-matrix fetch could not be completed within the tool budget, but the installed lockfile's node >= 20.9.0 engine declaration is the authoritative floor and Node 24 satisfies it.
  • No other unknowns: no image digest changes in the diff, no linked issues to compare against, and no evidence-provider findings were present in the corpus.
Sources
  • Next.js v16.3.1 release notes: https://github.com/vercel/next.js/releases/tag/v16.3.1
  • GitHub compare metadata for v16.3.0...v16.3.1 (22 commits, all backports)
  • Repository files read: Dockerfile (node:24-bookworm-slim), package.json (engines >=24, override rationale), and the updated package-lock.json entries.
@joryirving
joryirving
merged commit 0aa4c84
into
mainAug 14, 2026

7 checks passed

@joryirving
joryirving
deleted the

renovate/nextjs-monorepo

branch
August 14, 2026 00:22
@joryirvingjoryirving
mentioned this pull request
Aug 14, 2026
 Merged

@its-saffronits-saffronBot
mentioned this pull request
Aug 19, 2026
 Merged

Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@its-saffronits-saffron[bot]its-saffron[bot] approved these changes
@joryirvingjoryirvingAwaiting requested review from joryirvingjoryirving is a code owner

Assignees


No one assigned


Labels

type/patch

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

1 participant

@joryirving

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms");
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
fix(deps): update nextjs monorepo (16.3.0 → 16.3.1) - #767
Merged
joryirving merged 1 commit into
mainfrom 
renovate/nextjs-monorepo
Aug 14, 2026
Merged
fix(deps): update nextjs monorepo (16.3.0 → 16.3.1)#767
joryirving merged 1 commit into
mainfrom 
renovate/nextjs-monorepo
Conversation
@its-miso
@its-misoits-misoBot
commented
Aug 13, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
This PR contains the following updates:
PackageChangeAgeAdoptionPassingConfidence
eslint-config-next (source)16.3.0 → 16.3.1ageadoptionpassingconfidence
next (source)16.3.0 → 16.3.1ageadoptionpassingconfidence
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
vercel/next.js (eslint-config-next)
v16.3.1
Compare Source
What's Changed
Full Changelog: vercel/next.js@v16.3.0...v16.3.1
Configuration
📅 Schedule: (in timezone America/Edmonton)
  • Branch creation

    • At any time (no schedule defined)
  • Automerge

    • At any time (no schedule defined)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
  •  If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate CLI.
@its-miso
its-misoBot
requested a review
from joryirving
as a code ownerAugust 13, 2026 22:42
its-saffron[bot]

This comment was marked as outdated.

Sign in to view
@its-miso
its-misoBotforce-pushed
the
renovate/nextjs-monorepo
branch
from
1a53000 to
2f8ca61CompareAugust 13, 2026 23:41
@its-misoits-misoBot
changed the title
fix(deps): update dependency eslint-config-next (16.3.0 → 16.3.1)fix(deps): update nextjs monorepo (16.3.0 → 16.3.1)Aug 13, 2026
its-saffron[bot]
its-saffronBot
approved these changes
Aug 13, 2026
View reviewed changes
@its-saffronits-saffronBot
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AI Automated Review
Full PR review.
Analysis engine: dsv4f@https://litellm.jory.dev/v1 (openai) — primary route
Recommendation: Approve. This Renovate PR bumps the Next.js monorepo (next, eslint-config-next, @next/env, @next/eslint-plugin-next, the @next/swc-* platform binaries, and @swc/helpers) from 16.3.0 to 16.3.1, entirely within package-lock.json. No source, manifest, or Dockerfile changes. CI is green on the head commit, and the upstream 16.3.1 release is a patch-level set of backported fixes with no API or engine changes.
Change-by-change findings
  • package-lock.json — next 16.3.0 → 16.3.1 together with its matched dependencies: @next/env 16.3.1, @next/eslint-plugin-next 16.3.1, eslint-config-next 16.3.1, all eight @next/swc-* optional platform binaries at 16.3.1, and @swc/helpers 0.5.15 → 0.5.23 (bumped upstream in this same release). Every package moves in lockstep from a single published release, so there is no version skew between next and its native binaries on any target platform (linux musl/gnu, darwin, win32).
  • The PR title names only eslint-config-next, but the diff also updates the runtime next package and its dependencies; this is consistent with Renovate's nextjs-monorepo grouping and the lockfile is internally coherent.
  • Release evidence (Next.js v16.3.1, published 2026-08-13): all 22 commits are backported fixes on the 16.3 branch — Turbopack runtime/HMR and module-registration fixes, a next/image response-preservation fix, a styled-jsx Pages Router SSR fix, cache-tag/revalidation and unstable_cache naming fixes, a dev-validation worker fix, and a revert of an i18n localization change for dynamic Pages API routes. No public API changes, no peerDependency changes, and no breaking changes are listed; the installed lockfile metadata retains engines.node >= 20.9.0 unchanged.
  • The i18n revert applies to dynamic Pages Router API routes, while Dispatch uses the App Router (per AGENTS.md tech stack), so this revert is not expected to affect this application.
  • Host-platform coupling check: the Dockerfile pins the runtime to node:24-bookworm-slim and package.json declares engines.node >= 24; the installed next@16.3.1 declares node >= 20.9.0, so Node 24 is within the supported range. The lockfile engines field for the exact installed version is the binding constraint and it is satisfied.
  • Override coherence: next@16.3.1 still carries postcss 8.5.23 and optional sharp ^0.35.3, so the documented postcss/sharp override rationale in package.json remains accurate after this bump.
Standards Compliance
The change conforms to AGENTS.md: lockfile-only dependency update with no environment-variable, Prisma-schema, or Docker-base-image changes; the Docker npm ci stages consume the updated lockfile as-is; lint and typecheck gates still block CI and both passed.
Tool Harness Findings
CI on head commit 2f8ca61 reached a terminal success state for all checks: Build, Docker Build, Lint, Tests, Typecheck, and npm audit — all success. This directly satisfies the must-check "run full test suite after upgrade."
Unknowns or Needs Verification
  • The "check for breaking API changes" must-check is satisfied from the component's own release evidence: a patch release with backported fixes only, no API or engine changes. A separate Node.js compatibility-matrix fetch could not be completed within the tool budget, but the installed lockfile's node >= 20.9.0 engine declaration is the authoritative floor and Node 24 satisfies it.
  • No other unknowns: no image digest changes in the diff, no linked issues to compare against, and no evidence-provider findings were present in the corpus.
Sources
  • Next.js v16.3.1 release notes: https://github.com/vercel/next.js/releases/tag/v16.3.1
  • GitHub compare metadata for v16.3.0...v16.3.1 (22 commits, all backports)
  • Repository files read: Dockerfile (node:24-bookworm-slim), package.json (engines >=24, override rationale), and the updated package-lock.json entries.
@joryirving
joryirving
merged commit 0aa4c84
into
mainAug 14, 2026

7 checks passed

@joryirving
joryirving
deleted the

renovate/nextjs-monorepo

branch
August 14, 2026 00:22
@joryirvingjoryirving
mentioned this pull request
Aug 14, 2026
 Merged

@its-saffronits-saffronBot
mentioned this pull request
Aug 19, 2026
 Merged

Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@its-saffronits-saffron[bot]its-saffron[bot] approved these changes
@joryirvingjoryirvingAwaiting requested review from joryirvingjoryirving is a code owner

Assignees


No one assigned


Labels

type/patch

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

1 participant

@joryirving

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links");
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '

Skip to content
fix(deps): update nextjs monorepo (16.3.0 → 16.3.1) - #767
Merged
joryirving merged 1 commit into
mainfrom 
renovate/nextjs-monorepo
Aug 14, 2026
Merged
fix(deps): update nextjs monorepo (16.3.0 → 16.3.1)#767
joryirving merged 1 commit into
mainfrom 
renovate/nextjs-monorepo
Conversation
@its-miso
@its-misoits-misoBot
commented
Aug 13, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
This PR contains the following updates:
PackageChangeAgeAdoptionPassingConfidence
eslint-config-next (source)16.3.0 → 16.3.1ageadoptionpassingconfidence
next (source)16.3.0 → 16.3.1ageadoptionpassingconfidence
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
vercel/next.js (eslint-config-next)
v16.3.1
Compare Source
What's Changed
Full Changelog: vercel/next.js@v16.3.0...v16.3.1
Configuration
📅 Schedule: (in timezone America/Edmonton)
  • Branch creation

    • At any time (no schedule defined)
  • Automerge

    • At any time (no schedule defined)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
  •  If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate CLI.
@its-miso
its-misoBot
requested a review
from joryirving
as a code ownerAugust 13, 2026 22:42
its-saffron[bot]

This comment was marked as outdated.

Sign in to view
@its-miso
its-misoBotforce-pushed
the
renovate/nextjs-monorepo
branch
from
1a53000 to
2f8ca61CompareAugust 13, 2026 23:41
@its-misoits-misoBot
changed the title
fix(deps): update dependency eslint-config-next (16.3.0 → 16.3.1)fix(deps): update nextjs monorepo (16.3.0 → 16.3.1)Aug 13, 2026
its-saffron[bot]
its-saffronBot
approved these changes
Aug 13, 2026
View reviewed changes
@its-saffronits-saffronBot
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AI Automated Review
Full PR review.
Analysis engine: dsv4f@https://litellm.jory.dev/v1 (openai) — primary route
Recommendation: Approve. This Renovate PR bumps the Next.js monorepo (next, eslint-config-next, @next/env, @next/eslint-plugin-next, the @next/swc-* platform binaries, and @swc/helpers) from 16.3.0 to 16.3.1, entirely within package-lock.json. No source, manifest, or Dockerfile changes. CI is green on the head commit, and the upstream 16.3.1 release is a patch-level set of backported fixes with no API or engine changes.
Change-by-change findings
  • package-lock.json — next 16.3.0 → 16.3.1 together with its matched dependencies: @next/env 16.3.1, @next/eslint-plugin-next 16.3.1, eslint-config-next 16.3.1, all eight @next/swc-* optional platform binaries at 16.3.1, and @swc/helpers 0.5.15 → 0.5.23 (bumped upstream in this same release). Every package moves in lockstep from a single published release, so there is no version skew between next and its native binaries on any target platform (linux musl/gnu, darwin, win32).
  • The PR title names only eslint-config-next, but the diff also updates the runtime next package and its dependencies; this is consistent with Renovate's nextjs-monorepo grouping and the lockfile is internally coherent.
  • Release evidence (Next.js v16.3.1, published 2026-08-13): all 22 commits are backported fixes on the 16.3 branch — Turbopack runtime/HMR and module-registration fixes, a next/image response-preservation fix, a styled-jsx Pages Router SSR fix, cache-tag/revalidation and unstable_cache naming fixes, a dev-validation worker fix, and a revert of an i18n localization change for dynamic Pages API routes. No public API changes, no peerDependency changes, and no breaking changes are listed; the installed lockfile metadata retains engines.node >= 20.9.0 unchanged.
  • The i18n revert applies to dynamic Pages Router API routes, while Dispatch uses the App Router (per AGENTS.md tech stack), so this revert is not expected to affect this application.
  • Host-platform coupling check: the Dockerfile pins the runtime to node:24-bookworm-slim and package.json declares engines.node >= 24; the installed next@16.3.1 declares node >= 20.9.0, so Node 24 is within the supported range. The lockfile engines field for the exact installed version is the binding constraint and it is satisfied.
  • Override coherence: next@16.3.1 still carries postcss 8.5.23 and optional sharp ^0.35.3, so the documented postcss/sharp override rationale in package.json remains accurate after this bump.
Standards Compliance
The change conforms to AGENTS.md: lockfile-only dependency update with no environment-variable, Prisma-schema, or Docker-base-image changes; the Docker npm ci stages consume the updated lockfile as-is; lint and typecheck gates still block CI and both passed.
Tool Harness Findings
CI on head commit 2f8ca61 reached a terminal success state for all checks: Build, Docker Build, Lint, Tests, Typecheck, and npm audit — all success. This directly satisfies the must-check "run full test suite after upgrade."
Unknowns or Needs Verification
  • The "check for breaking API changes" must-check is satisfied from the component's own release evidence: a patch release with backported fixes only, no API or engine changes. A separate Node.js compatibility-matrix fetch could not be completed within the tool budget, but the installed lockfile's node >= 20.9.0 engine declaration is the authoritative floor and Node 24 satisfies it.
  • No other unknowns: no image digest changes in the diff, no linked issues to compare against, and no evidence-provider findings were present in the corpus.
Sources
  • Next.js v16.3.1 release notes: https://github.com/vercel/next.js/releases/tag/v16.3.1
  • GitHub compare metadata for v16.3.0...v16.3.1 (22 commits, all backports)
  • Repository files read: Dockerfile (node:24-bookworm-slim), package.json (engines >=24, override rationale), and the updated package-lock.json entries.
@joryirving
joryirving
merged commit 0aa4c84
into
mainAug 14, 2026

7 checks passed

@joryirving
joryirving
deleted the

renovate/nextjs-monorepo

branch
August 14, 2026 00:22
@joryirvingjoryirving
mentioned this pull request
Aug 14, 2026
 Merged

@its-saffronits-saffronBot
mentioned this pull request
Aug 19, 2026
 Merged

Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@its-saffronits-saffron[bot]its-saffron[bot] approved these changes
@joryirvingjoryirvingAwaiting requested review from joryirvingjoryirving is a code owner

Assignees


No one assigned


Labels

type/patch

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

1 participant

@joryirving

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default");
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
fix(deps): update nextjs monorepo (16.3.0 → 16.3.1) - #767
Merged
joryirving merged 1 commit into
mainfrom 
renovate/nextjs-monorepo
Aug 14, 2026
Merged
fix(deps): update nextjs monorepo (16.3.0 → 16.3.1)#767
joryirving merged 1 commit into
mainfrom 
renovate/nextjs-monorepo
Conversation
@its-miso
@its-misoits-misoBot
commented
Aug 13, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
This PR contains the following updates:
PackageChangeAgeAdoptionPassingConfidence
eslint-config-next (source)16.3.0 → 16.3.1ageadoptionpassingconfidence
next (source)16.3.0 → 16.3.1ageadoptionpassingconfidence
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
vercel/next.js (eslint-config-next)
v16.3.1
Compare Source
What's Changed
Full Changelog: vercel/next.js@v16.3.0...v16.3.1
Configuration
📅 Schedule: (in timezone America/Edmonton)
  • Branch creation

    • At any time (no schedule defined)
  • Automerge

    • At any time (no schedule defined)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
  •  If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate CLI.
@its-miso
its-misoBot
requested a review
from joryirving
as a code ownerAugust 13, 2026 22:42
its-saffron[bot]

This comment was marked as outdated.

Sign in to view
@its-miso
its-misoBotforce-pushed
the
renovate/nextjs-monorepo
branch
from
1a53000 to
2f8ca61CompareAugust 13, 2026 23:41
@its-misoits-misoBot
changed the title
fix(deps): update dependency eslint-config-next (16.3.0 → 16.3.1)fix(deps): update nextjs monorepo (16.3.0 → 16.3.1)Aug 13, 2026
its-saffron[bot]
its-saffronBot
approved these changes
Aug 13, 2026
View reviewed changes
@its-saffronits-saffronBot
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AI Automated Review
Full PR review.
Analysis engine: dsv4f@https://litellm.jory.dev/v1 (openai) — primary route
Recommendation: Approve. This Renovate PR bumps the Next.js monorepo (next, eslint-config-next, @next/env, @next/eslint-plugin-next, the @next/swc-* platform binaries, and @swc/helpers) from 16.3.0 to 16.3.1, entirely within package-lock.json. No source, manifest, or Dockerfile changes. CI is green on the head commit, and the upstream 16.3.1 release is a patch-level set of backported fixes with no API or engine changes.
Change-by-change findings
  • package-lock.json — next 16.3.0 → 16.3.1 together with its matched dependencies: @next/env 16.3.1, @next/eslint-plugin-next 16.3.1, eslint-config-next 16.3.1, all eight @next/swc-* optional platform binaries at 16.3.1, and @swc/helpers 0.5.15 → 0.5.23 (bumped upstream in this same release). Every package moves in lockstep from a single published release, so there is no version skew between next and its native binaries on any target platform (linux musl/gnu, darwin, win32).
  • The PR title names only eslint-config-next, but the diff also updates the runtime next package and its dependencies; this is consistent with Renovate's nextjs-monorepo grouping and the lockfile is internally coherent.
  • Release evidence (Next.js v16.3.1, published 2026-08-13): all 22 commits are backported fixes on the 16.3 branch — Turbopack runtime/HMR and module-registration fixes, a next/image response-preservation fix, a styled-jsx Pages Router SSR fix, cache-tag/revalidation and unstable_cache naming fixes, a dev-validation worker fix, and a revert of an i18n localization change for dynamic Pages API routes. No public API changes, no peerDependency changes, and no breaking changes are listed; the installed lockfile metadata retains engines.node >= 20.9.0 unchanged.
  • The i18n revert applies to dynamic Pages Router API routes, while Dispatch uses the App Router (per AGENTS.md tech stack), so this revert is not expected to affect this application.
  • Host-platform coupling check: the Dockerfile pins the runtime to node:24-bookworm-slim and package.json declares engines.node >= 24; the installed next@16.3.1 declares node >= 20.9.0, so Node 24 is within the supported range. The lockfile engines field for the exact installed version is the binding constraint and it is satisfied.
  • Override coherence: next@16.3.1 still carries postcss 8.5.23 and optional sharp ^0.35.3, so the documented postcss/sharp override rationale in package.json remains accurate after this bump.
Standards Compliance
The change conforms to AGENTS.md: lockfile-only dependency update with no environment-variable, Prisma-schema, or Docker-base-image changes; the Docker npm ci stages consume the updated lockfile as-is; lint and typecheck gates still block CI and both passed.
Tool Harness Findings
CI on head commit 2f8ca61 reached a terminal success state for all checks: Build, Docker Build, Lint, Tests, Typecheck, and npm audit — all success. This directly satisfies the must-check "run full test suite after upgrade."
Unknowns or Needs Verification
  • The "check for breaking API changes" must-check is satisfied from the component's own release evidence: a patch release with backported fixes only, no API or engine changes. A separate Node.js compatibility-matrix fetch could not be completed within the tool budget, but the installed lockfile's node >= 20.9.0 engine declaration is the authoritative floor and Node 24 satisfies it.
  • No other unknowns: no image digest changes in the diff, no linked issues to compare against, and no evidence-provider findings were present in the corpus.
Sources
  • Next.js v16.3.1 release notes: https://github.com/vercel/next.js/releases/tag/v16.3.1
  • GitHub compare metadata for v16.3.0...v16.3.1 (22 commits, all backports)
  • Repository files read: Dockerfile (node:24-bookworm-slim), package.json (engines >=24, override rationale), and the updated package-lock.json entries.
@joryirving
joryirving
merged commit 0aa4c84
into
mainAug 14, 2026

7 checks passed

@joryirving
joryirving
deleted the

renovate/nextjs-monorepo

branch
August 14, 2026 00:22
@joryirvingjoryirving
mentioned this pull request
Aug 14, 2026
 Merged

@its-saffronits-saffronBot
mentioned this pull request
Aug 19, 2026
 Merged

Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@its-saffronits-saffron[bot]its-saffron[bot] approved these changes
@joryirvingjoryirvingAwaiting requested review from joryirvingjoryirving is a code owner

Assignees


No one assigned


Labels

type/patch

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

1 participant

@joryirving

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers");
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
fix(deps): update nextjs monorepo (16.3.0 → 16.3.1) - #767
Merged
joryirving merged 1 commit into
mainfrom 
renovate/nextjs-monorepo
Aug 14, 2026
Merged
fix(deps): update nextjs monorepo (16.3.0 → 16.3.1)#767
joryirving merged 1 commit into
mainfrom 
renovate/nextjs-monorepo
Conversation
@its-miso
@its-misoits-misoBot
commented
Aug 13, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
This PR contains the following updates:
PackageChangeAgeAdoptionPassingConfidence
eslint-config-next (source)16.3.0 → 16.3.1ageadoptionpassingconfidence
next (source)16.3.0 → 16.3.1ageadoptionpassingconfidence
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
vercel/next.js (eslint-config-next)
v16.3.1
Compare Source
What's Changed
Full Changelog: vercel/next.js@v16.3.0...v16.3.1
Configuration
📅 Schedule: (in timezone America/Edmonton)
  • Branch creation

    • At any time (no schedule defined)
  • Automerge

    • At any time (no schedule defined)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
  •  If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate CLI.
@its-miso
its-misoBot
requested a review
from joryirving
as a code ownerAugust 13, 2026 22:42
its-saffron[bot]

This comment was marked as outdated.

Sign in to view
@its-miso
its-misoBotforce-pushed
the
renovate/nextjs-monorepo
branch
from
1a53000 to
2f8ca61CompareAugust 13, 2026 23:41
@its-misoits-misoBot
changed the title
fix(deps): update dependency eslint-config-next (16.3.0 → 16.3.1)fix(deps): update nextjs monorepo (16.3.0 → 16.3.1)Aug 13, 2026
its-saffron[bot]
its-saffronBot
approved these changes
Aug 13, 2026
View reviewed changes
@its-saffronits-saffronBot
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AI Automated Review
Full PR review.
Analysis engine: dsv4f@https://litellm.jory.dev/v1 (openai) — primary route
Recommendation: Approve. This Renovate PR bumps the Next.js monorepo (next, eslint-config-next, @next/env, @next/eslint-plugin-next, the @next/swc-* platform binaries, and @swc/helpers) from 16.3.0 to 16.3.1, entirely within package-lock.json. No source, manifest, or Dockerfile changes. CI is green on the head commit, and the upstream 16.3.1 release is a patch-level set of backported fixes with no API or engine changes.
Change-by-change findings
  • package-lock.json — next 16.3.0 → 16.3.1 together with its matched dependencies: @next/env 16.3.1, @next/eslint-plugin-next 16.3.1, eslint-config-next 16.3.1, all eight @next/swc-* optional platform binaries at 16.3.1, and @swc/helpers 0.5.15 → 0.5.23 (bumped upstream in this same release). Every package moves in lockstep from a single published release, so there is no version skew between next and its native binaries on any target platform (linux musl/gnu, darwin, win32).
  • The PR title names only eslint-config-next, but the diff also updates the runtime next package and its dependencies; this is consistent with Renovate's nextjs-monorepo grouping and the lockfile is internally coherent.
  • Release evidence (Next.js v16.3.1, published 2026-08-13): all 22 commits are backported fixes on the 16.3 branch — Turbopack runtime/HMR and module-registration fixes, a next/image response-preservation fix, a styled-jsx Pages Router SSR fix, cache-tag/revalidation and unstable_cache naming fixes, a dev-validation worker fix, and a revert of an i18n localization change for dynamic Pages API routes. No public API changes, no peerDependency changes, and no breaking changes are listed; the installed lockfile metadata retains engines.node >= 20.9.0 unchanged.
  • The i18n revert applies to dynamic Pages Router API routes, while Dispatch uses the App Router (per AGENTS.md tech stack), so this revert is not expected to affect this application.
  • Host-platform coupling check: the Dockerfile pins the runtime to node:24-bookworm-slim and package.json declares engines.node >= 24; the installed next@16.3.1 declares node >= 20.9.0, so Node 24 is within the supported range. The lockfile engines field for the exact installed version is the binding constraint and it is satisfied.
  • Override coherence: next@16.3.1 still carries postcss 8.5.23 and optional sharp ^0.35.3, so the documented postcss/sharp override rationale in package.json remains accurate after this bump.
Standards Compliance
The change conforms to AGENTS.md: lockfile-only dependency update with no environment-variable, Prisma-schema, or Docker-base-image changes; the Docker npm ci stages consume the updated lockfile as-is; lint and typecheck gates still block CI and both passed.
Tool Harness Findings
CI on head commit 2f8ca61 reached a terminal success state for all checks: Build, Docker Build, Lint, Tests, Typecheck, and npm audit — all success. This directly satisfies the must-check "run full test suite after upgrade."
Unknowns or Needs Verification
  • The "check for breaking API changes" must-check is satisfied from the component's own release evidence: a patch release with backported fixes only, no API or engine changes. A separate Node.js compatibility-matrix fetch could not be completed within the tool budget, but the installed lockfile's node >= 20.9.0 engine declaration is the authoritative floor and Node 24 satisfies it.
  • No other unknowns: no image digest changes in the diff, no linked issues to compare against, and no evidence-provider findings were present in the corpus.
Sources
  • Next.js v16.3.1 release notes: https://github.com/vercel/next.js/releases/tag/v16.3.1
  • GitHub compare metadata for v16.3.0...v16.3.1 (22 commits, all backports)
  • Repository files read: Dockerfile (node:24-bookworm-slim), package.json (engines >=24, override rationale), and the updated package-lock.json entries.
@joryirving
joryirving
merged commit 0aa4c84
into
mainAug 14, 2026

7 checks passed

@joryirving
joryirving
deleted the

renovate/nextjs-monorepo

branch
August 14, 2026 00:22
@joryirvingjoryirving
mentioned this pull request
Aug 14, 2026
 Merged

@its-saffronits-saffronBot
mentioned this pull request
Aug 19, 2026
 Merged

Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@its-saffronits-saffron[bot]its-saffron[bot] approved these changes
@joryirvingjoryirvingAwaiting requested review from joryirvingjoryirving is a code owner

Assignees


No one assigned


Labels

type/patch

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

1 participant

@joryirving

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode");
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();

Skip to content
fix(deps): update nextjs monorepo (16.3.0 → 16.3.1) - #767
Merged
joryirving merged 1 commit into
mainfrom 
renovate/nextjs-monorepo
Aug 14, 2026
Merged
fix(deps): update nextjs monorepo (16.3.0 → 16.3.1)#767
joryirving merged 1 commit into
mainfrom 
renovate/nextjs-monorepo
Conversation
@its-miso
@its-misoits-misoBot
commented
Aug 13, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
This PR contains the following updates:
PackageChangeAgeAdoptionPassingConfidence
eslint-config-next (source)16.3.0 → 16.3.1ageadoptionpassingconfidence
next (source)16.3.0 → 16.3.1ageadoptionpassingconfidence
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
vercel/next.js (eslint-config-next)
v16.3.1
Compare Source
What's Changed
Full Changelog: vercel/next.js@v16.3.0...v16.3.1
Configuration
📅 Schedule: (in timezone America/Edmonton)
  • Branch creation

    • At any time (no schedule defined)
  • Automerge

    • At any time (no schedule defined)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
  •  If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate CLI.
@its-miso
its-misoBot
requested a review
from joryirving
as a code ownerAugust 13, 2026 22:42
its-saffron[bot]

This comment was marked as outdated.

Sign in to view
@its-miso
its-misoBotforce-pushed
the
renovate/nextjs-monorepo
branch
from
1a53000 to
2f8ca61CompareAugust 13, 2026 23:41
@its-misoits-misoBot
changed the title
fix(deps): update dependency eslint-config-next (16.3.0 → 16.3.1)fix(deps): update nextjs monorepo (16.3.0 → 16.3.1)Aug 13, 2026
its-saffron[bot]
its-saffronBot
approved these changes
Aug 13, 2026
View reviewed changes
@its-saffronits-saffronBot
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AI Automated Review
Full PR review.
Analysis engine: dsv4f@https://litellm.jory.dev/v1 (openai) — primary route
Recommendation: Approve. This Renovate PR bumps the Next.js monorepo (next, eslint-config-next, @next/env, @next/eslint-plugin-next, the @next/swc-* platform binaries, and @swc/helpers) from 16.3.0 to 16.3.1, entirely within package-lock.json. No source, manifest, or Dockerfile changes. CI is green on the head commit, and the upstream 16.3.1 release is a patch-level set of backported fixes with no API or engine changes.
Change-by-change findings
  • package-lock.json — next 16.3.0 → 16.3.1 together with its matched dependencies: @next/env 16.3.1, @next/eslint-plugin-next 16.3.1, eslint-config-next 16.3.1, all eight @next/swc-* optional platform binaries at 16.3.1, and @swc/helpers 0.5.15 → 0.5.23 (bumped upstream in this same release). Every package moves in lockstep from a single published release, so there is no version skew between next and its native binaries on any target platform (linux musl/gnu, darwin, win32).
  • The PR title names only eslint-config-next, but the diff also updates the runtime next package and its dependencies; this is consistent with Renovate's nextjs-monorepo grouping and the lockfile is internally coherent.
  • Release evidence (Next.js v16.3.1, published 2026-08-13): all 22 commits are backported fixes on the 16.3 branch — Turbopack runtime/HMR and module-registration fixes, a next/image response-preservation fix, a styled-jsx Pages Router SSR fix, cache-tag/revalidation and unstable_cache naming fixes, a dev-validation worker fix, and a revert of an i18n localization change for dynamic Pages API routes. No public API changes, no peerDependency changes, and no breaking changes are listed; the installed lockfile metadata retains engines.node >= 20.9.0 unchanged.
  • The i18n revert applies to dynamic Pages Router API routes, while Dispatch uses the App Router (per AGENTS.md tech stack), so this revert is not expected to affect this application.
  • Host-platform coupling check: the Dockerfile pins the runtime to node:24-bookworm-slim and package.json declares engines.node >= 24; the installed next@16.3.1 declares node >= 20.9.0, so Node 24 is within the supported range. The lockfile engines field for the exact installed version is the binding constraint and it is satisfied.
  • Override coherence: next@16.3.1 still carries postcss 8.5.23 and optional sharp ^0.35.3, so the documented postcss/sharp override rationale in package.json remains accurate after this bump.
Standards Compliance
The change conforms to AGENTS.md: lockfile-only dependency update with no environment-variable, Prisma-schema, or Docker-base-image changes; the Docker npm ci stages consume the updated lockfile as-is; lint and typecheck gates still block CI and both passed.
Tool Harness Findings
CI on head commit 2f8ca61 reached a terminal success state for all checks: Build, Docker Build, Lint, Tests, Typecheck, and npm audit — all success. This directly satisfies the must-check "run full test suite after upgrade."
Unknowns or Needs Verification
  • The "check for breaking API changes" must-check is satisfied from the component's own release evidence: a patch release with backported fixes only, no API or engine changes. A separate Node.js compatibility-matrix fetch could not be completed within the tool budget, but the installed lockfile's node >= 20.9.0 engine declaration is the authoritative floor and Node 24 satisfies it.
  • No other unknowns: no image digest changes in the diff, no linked issues to compare against, and no evidence-provider findings were present in the corpus.
Sources
  • Next.js v16.3.1 release notes: https://github.com/vercel/next.js/releases/tag/v16.3.1
  • GitHub compare metadata for v16.3.0...v16.3.1 (22 commits, all backports)
  • Repository files read: Dockerfile (node:24-bookworm-slim), package.json (engines >=24, override rationale), and the updated package-lock.json entries.
@joryirving
joryirving
merged commit 0aa4c84
into
mainAug 14, 2026

7 checks passed

@joryirving
joryirving
deleted the

renovate/nextjs-monorepo

branch
August 14, 2026 00:22
@joryirvingjoryirving
mentioned this pull request
Aug 14, 2026
 Merged

@its-saffronits-saffronBot
mentioned this pull request
Aug 19, 2026
 Merged

Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@its-saffronits-saffron[bot]its-saffron[bot] approved these changes
@joryirvingjoryirvingAwaiting requested review from joryirvingjoryirving is a code owner

Assignees


No one assigned


Labels

type/patch

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

1 participant

@joryirving