Repository navigation
chore(deps-dev): Bump @types/node in /examples/chat/frontend-next - #1611
Merged
pathosDev merged 1 commit intoSep 20, 2026
Conversation
Bumps [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) in `/examples/chat/frontend-next` from 22.20.1 to 26.6.1. Updates `@types/node` from 22.20.1 to 26.6.1 - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node) Updates `@types/node` from 22.20.1 to 26.6.1 - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node) --- updated-dependencies: - dependency-name: "@types/node" dependency-version: 26.6.1 dependency-type: direct:development update-type: version-update:semver-major dependency-group: npm_and_yarn - dependency-name: "@types/node" dependency-version: 26.6.1 dependency-type: direct:development update-type: version-update:semver-major dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com>
pathosDev
added a commit
that referenced
this pull request
Sep 20, 2026
…s/node 26 bump Dependabot's per-dependency group (#1611) moves `@types/node` from 22 to 26 in both Next frontends, in the manifest and `package-lock.json`; the `bun.lock` beside them is regenerated with `bun install --lockfile-only` so `examples.yml`'s frozen dry-run passes (it resolves the caret to 26.6.2 where npm pinned 26.6.1 — the two-lockfile drift #1402 is about). The root's `@types/node` floor is a library concern; these are demo apps, and `next build` type-checks both against the new types cleanly: `npm ci` and `npm run build` pass in both directories, on top of the Angular/Next/Vite group merged from develop. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
dependabot
Bot
deleted the
dependabot/npm_and_yarn/examples/chat/frontend-next/npm_and_yarn-0e1c956402
branch
September 20, 2026 01:28
pathosDev
added a commit
that referenced
this pull request
Sep 20, 2026
…he root — and hold it #1601 took `/docs`' `@types/node` from `^24.13.3` to `^26.6.1`, and the Dependabot config let it through on purpose: TypeDoc compiles `../src` with the root tsconfig, so the root's pin guards the library and the docs copy only types the site's own files. Correct about the library, and still types for a Node the docs never run on — every workflow sets up 24 and `engines.node` is `>=24`. One Node story instead: `@types/node` declares the floor's major in every Bun-installed manifest that has it. `/docs` goes back to `^24.13.3` (bun.lock regenerated, stamp still 1), the `/docs` Dependabot entry carries the root's semver-major `ignore` and says why the exemption was withdrawn, and `tests/unit/ci/TypesNodeFloor.test.ts` holds the three things together that nothing under `tests/` had pinned: the declared major equals the `engines` floor in every Bun manifest declaring the package, every such entry ignores the majors, and every workflow's `node-version` is the floor. Verified to fail against develop's state on the first two and to pass after the revert. The Next example frontends (26 as of #1611, 22 before) are npm-installed demo apps and out of scope. Closes #1616 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
pathosDev
added a commit
that referenced
this pull request
Sep 20, 2026
…24 floor too The Next frontends were the last manifests off the floor: `@types/node` had gone 22 → 26 on the first day of the npm Dependabot entry (#1611), types for a Node that `examples.yml` never sets up. Both go to `^24.13.3` — `package-lock.json` regenerated with `npm install --package-lock-only`, `bun.lock` with `bun install --lockfile-only`, the two agreeing on 24.13.6 and the stamp staying 1 — and the npm entry carries the same semver-major `ignore` as the root and `/docs`. `TypesNodeFloor.test.ts` now reads the npm entry's `directories:` list as well, so the frontends are in the same story as everything else; it fails against the previous state on both the manifests and the missing rule, and passes after. `npm ci` and `npm run build` pass in both directories. Refs #1616 Co-Authored-By: Claude Opus 5 <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 @types/node in
/examples/chat/frontend-nextfrom 22.20.1 to 26.6.1.Updates
@types/nodefrom 22.20.1 to 26.6.1Commits
Updates
@types/nodefrom 22.20.1 to 26.6.1Commits
Dependabot 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