chore(deps): bump the development-dependencies group with 4 updates - #282
Merged
StuartMeeks merged 1 commit intoAug 6, 2026
Merged
Conversation
Bumps the development-dependencies group with 4 updates: [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node), [@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react/tree/HEAD/packages/plugin-react), [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) and [tsx](https://github.com/privatenumber/tsx). Updates `@types/node` from 26.1.1 to 26.1.2 - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node) Updates `@vitejs/plugin-react` from 6.0.4 to 6.0.5 - [Release notes](https://github.com/vitejs/vite-plugin-react/releases) - [Changelog](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-react/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite-plugin-react/commits/plugin-react@6.0.5/packages/plugin-react) Updates `vite` from 8.1.5 to 8.2.0 - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/create-vite@8.2.0/packages/vite) Updates `tsx` from 4.23.1 to 4.23.5 - [Release notes](https://github.com/privatenumber/tsx/releases) - [Changelog](https://github.com/privatenumber/tsx/blob/master/release.config.cjs) - [Commits](privatenumber/tsx@v4.23.1...v4.23.5) --- updated-dependencies: - dependency-name: "@types/node" dependency-version: 26.1.2 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: development-dependencies - dependency-name: "@vitejs/plugin-react" dependency-version: 6.0.5 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: development-dependencies - dependency-name: vite dependency-version: 8.2.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: development-dependencies - dependency-name: tsx dependency-version: 4.23.5 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: development-dependencies ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
dependabot
Bot
added
dependencies
StuartMeeks
enabled auto-merge (squash)
August 6, 2026 12:56
StuartMeeks
approved these changes
Aug 6, 2026
StuartMeeks
deleted the
dependabot/npm_and_yarn/development-dependencies-3fac905919
branch
August 6, 2026 13:11
StuartMeeks
added a commit
that referenced
this pull request
Aug 6, 2026
#281 restored the queuing half of auto-merge but not the merging half. PR #282 proved it: every check green, statusCheckRollup SUCCESS, auto-merge enabled nine seconds after Dependabot opened it — and still BLOCKED, sitting at reviewDecision REVIEW_REQUIRED. The `main protection` ruleset requires a code-owner approval, and the assumption that a bypass actor could merge without one was wrong. Bypass applies only to an interactive merge performed by that actor (`gh pr merge --admin`); GitHub's auto-merge ignores bypass entirely and waits for every merge requirement, review included. Approving #282 by hand settled it — the queued merge completed on its own three seconds later, with no other change. Approve with AUTOMERGE_TOKEN before queuing the merge. CODEOWNERS makes @StuartMeeks the owner of every path, and GITHUB_TOKEN cannot stand in: the repository disallows Actions approvals and github-actions[bot] is not a code owner. The approval re-runs on `synchronize` because the ruleset dismisses stale reviews on push and requires the approval to follow the last push. Patch and minor bumps now merge without a human reading them. That is what auto-merge means here, but it is a real change in review posture, so the workflow header states it plainly. Majors still stop for review, and required checks are never bypassed — auto-merge continues to wait for build-test and validate-game-data. Also correct the header comment from #281, which described the bypass behaviour incorrectly.
StuartMeeks
added a commit
that referenced
this pull request
Aug 6, 2026
#281 restored the queuing half of auto-merge but not the merging half. PR #282 proved it: every check green, statusCheckRollup SUCCESS, auto-merge enabled nine seconds after Dependabot opened it — and still BLOCKED, sitting at reviewDecision REVIEW_REQUIRED. The `main protection` ruleset requires a code-owner approval, and the assumption that a bypass actor could merge without one was wrong. Bypass applies only to an interactive merge performed by that actor (`gh pr merge --admin`); GitHub's auto-merge ignores bypass entirely and waits for every merge requirement, review included. Approving #282 by hand settled it — the queued merge completed on its own three seconds later, with no other change. Approve with AUTOMERGE_TOKEN before queuing the merge. CODEOWNERS makes @StuartMeeks the owner of every path, and GITHUB_TOKEN cannot stand in: the repository disallows Actions approvals and github-actions[bot] is not a code owner. The approval re-runs on `synchronize` because the ruleset dismisses stale reviews on push and requires the approval to follow the last push. Patch and minor bumps now merge without a human reading them. That is what auto-merge means here, but it is a real change in review posture, so the workflow header states it plainly. Majors still stop for review, and required checks are never bypassed — auto-merge continues to wait for build-test and validate-game-data. Also correct the header comment from #281, which described the bypass behaviour incorrectly.
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-dependencies group with 4 updates: @types/node, @vitejs/plugin-react, vite and tsx.
Updates
@types/nodefrom 26.1.1 to 26.1.2Commits
Updates
@vitejs/plugin-reactfrom 6.0.4 to 6.0.5Release notes
Sourced from @vitejs/plugin-react's releases.
Changelog
Sourced from @vitejs/plugin-react's changelog.
Commits
68c0cb8release: plugin-react@6.0.5 (#1362)555cdbcfix(react): make the react compiler preset filter linear (#1353)a00a9f8fix(deps): update all non-major dependencies (#1327)Updates
vitefrom 8.1.5 to 8.2.0Release notes
Sourced from vite's releases.
Changelog
Sourced from vite's changelog.
... (truncated)
Commits
24a611frelease: v7.2.42d66b7bfix: revert "perf(deps): replace debug with obug (#21107)"a668014release: v7.2.3acfe939perf(deps): replace debug with obug (#21107)4f8171efix(deps): update all non-major dependencies (#21128)5029720chore(deps): update rolldown-related dependencies (#21127)5909efdfix: allow multiplebindCLIShortcutscalls with shortcut merging (#21103)39a0a15chore(deps): update rolldown-related dependencies (#21095)6a34ac3fix(deps): update all non-major dependencies (#21096)02ceaecchore(deps): update dependency@rollup/plugin-commonjsto v29 (#21099)Updates
tsxfrom 4.23.1 to 4.23.5Release notes
Sourced from tsx's releases.
Commits
c55004dtest: remove legacy PTY retrye368161chore(deps): update pty-spawn to 1.1.18d39496ci: validate GitHub Actions workflows6fe724etest: clean up timed-out PTY attemptse0a0536ci: skip unused Windows Node cache6d6dd84ci: remove broken lock automation3c1d051fix: detect the Node inspector enabled via NODE_OPTIONS40380a4ci: lock down the release toolchainf217b6bci: restrict releases to public repository2afc7bbfix(cli): allow async process.once() signal handlers to finish (#827)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