Repository navigation
chore: bump the web-development group in /web with 2 updates - #450
Merged
G1NG4R merged 2 commits intoOct 17, 2026
Merged
Conversation
Bumps the web-development group in /web with 2 updates: [@next/mdx](https://github.com/vercel/next.js/tree/HEAD/packages/next-mdx) and [eslint-config-next](https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next). Updates `@next/mdx` from 16.3.6 to 16.3.8 - [Release notes](https://github.com/vercel/next.js/releases) - [Commits](https://github.com/vercel/next.js/commits/v16.3.8/packages/next-mdx) Updates `eslint-config-next` from 16.3.6 to 16.3.8 - [Release notes](https://github.com/vercel/next.js/releases) - [Commits](https://github.com/vercel/next.js/commits/v16.3.8/packages/eslint-config-next) --- updated-dependencies: - dependency-name: "@next/mdx" dependency-version: 16.3.8 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: web-development - dependency-name: eslint-config-next dependency-version: 16.3.8 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: web-development ... Signed-off-by: dependabot[bot] <support@github.com>
G1NG4R
deleted the
dependabot/npm_and_yarn/web/web-development-b35f27f585
branch
October 17, 2026 00:41
G1NG4R
added a commit
that referenced
this pull request
Oct 17, 2026
Backlog only — no code. The night's measurements, including two corrections to figures I published a few hours ago. ## What it carries - **`e2e` on `main` runs 12:40 to 34:57, not to 17:38.** `944a1e4` took **34:57 and went green**, double the upper bound the entry below claims from six samples. Long does not mean red, which also retires the suspicion that a long `e2e` is one retrying a failure. The rule "start the witness as soon as `e2e` is `in_progress`" survives — it is the only start that still has lead time at 35 minutes — but the 1800 s rail does not, so both later runs used `WITNESS_MAX_SEC=2700`. - **A single read of `/api/health` can report a process that is already gone.** Nine seconds after the `944a1e4` deploy it reported `startedAt 00:39:53.604Z`, *before* `ops.lastDeploy.at` — the first negative offset of the series, and a finding-shaped one. Ten samples later the serving process is `00:40:16.706Z`, i.e. **+12.7 s**, squarely in the known band. During a rollout `/api/health` is balanced across two processes, so one read is a sample, not an identity. Same family as the stale-`p95` note in #452: there the number is old, here the process is. - **Two swaps, both clean:** 339 × 200 and 1087 × 200 per path, zero non-200. The first witness of the night ran its full 1800 s with no deploy in it; a chained successor took over with a **4 s gap** and logged the identity before starting, so the handover is proven rather than assumed. - **#453 now has four data points** and the pattern holds: coverage after the serving process comes up is 30 s minus the twin gap — 26.6 s → 3.4 s, 15.6 s → 14.4 s, 16.7 s → 13.3 s, 16.3 s → 13.7 s. The normal gap is around 16 s; the 26.6 s outlier is the one that shuts the window. - **#450's red `e2e` was the #429 count test**, and after `gh pr update-branch` the fresh run was green on its own — the one permitted rerun went unused. Its premise was checked in `.github/dependabot.yml`: `next`, `@next/mdx` and `eslint-config-next` are held for semver-**minor** only, so a 16.3.6 → 16.3.8 patch is what #445 intended to keep arriving. The idle-drop tally gains three rows and stands at 6 drops in roughly 35 440 requests, eleven swap runs in a row without one. #304 gains **no** new evidence from tonight: four witnessed swaps, all clean. `make check` green. Co-authored-by: Claude Code <noreply@anthropic.com>
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 web-development group in /web with 2 updates: @next/mdx and eslint-config-next.
Updates
@next/mdxfrom 16.3.6 to 16.3.8Release notes
Sourced from @next/mdx's releases.
Commits
b0fad0dv16.3.84c20699v16.3.7Updates
eslint-config-nextfrom 16.3.6 to 16.3.8Release notes
Sourced from eslint-config-next's releases.
Commits
b0fad0dv16.3.84c20699v16.3.7Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions