chore(deps-dev): bump @types/node from 24.13.3 to 26.1.1 in the development-toolchain group - #52
Merged
AetherAI3 merged 1 commit intoJul 23, 2026
Conversation
Bumps the development-toolchain group with 1 update: [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node). Updates `@types/node` from 24.13.3 to 26.1.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.1.1 dependency-type: direct:development update-type: version-update:semver-major dependency-group: development-toolchain ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
AetherAI3
deleted the
dependabot/npm_and_yarn/development-toolchain-cf49706eb9
branch
July 23, 2026 08:56
4 tasks
AetherAI3
added a commit
that referenced
this pull request
Jul 28, 2026
…@types/node (#57) Two loose ends from the LOOP-17 device-auth work. The CLI reported a denial as "authorization denied in the browser" — a verdict with no next step, which reads like the account was rejected rather than one request being refused. Denial is recoverable: nothing was authorized, no key was created, and re-running the command starts a fresh request. The message now says that. It also names the case the user cannot otherwise know about. A device request is bound to no one until someone acts on it, so any signed-in account that learns a user_code can refuse it. A denial the user did not perform therefore means their code reached somebody else, which is worth telling them while they still have the terminal open. This is the CLI half of the accepted-risk note in the 2026-07-28 phishing-resistance spec. Deliberately one line: formatErrorLine puts its glyph on the first line only, so a multi-line message loses it on every line after the first. The existing login.test.ts assertions pass unchanged. Also pins @types/node against major bumps in dependabot. It must track engines.node (">=24"), not the newest release — typing the project against a Node it does not claim to support lets tsc accept APIs that do not exist for users on the supported version, a type error that only surfaces at their runtime. migration_guard asserts the pairing, so a major bump lands as red CI on main; #52 did exactly that and main stayed broken until it was reverted. Minor and patch updates still flow. Tests: 823 pass, 0 fail. 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
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.
Bumps the development-toolchain group with 1 update: @types/node.
Updates
@types/nodefrom 24.13.3 to 26.1.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