chore(deps): update dependency web-ext to 10.6.0 - #2195
Open
github-actions[bot] wants to merge 1 commit into
Open
chore(deps): update dependency web-ext to 10.6.0#2195github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
changed the title
github-actions
Bot
force-pushed
the
buddy-bot/update-major-update-web-ext
branch
from
August 4, 2026 14:09
5b78923 to
0992758
Compare
5 tasks
chrisbbreuer
added a commit
that referenced
this pull request
Sep 10, 2026
…affold (#2574) AGENTS.md has always said buddy-bot handles dependency updates, not renovatebot. Four bots were running anyway, and 13 of 17 open pull requests were theirs. Two of them proposed the same bump twice - web-ext as #2194 and #2195, all-non-major as #1825 and #2202 - and a second dependency dashboard sat in #1, open since 2022. Every duplicate burns a full CI matrix and needs a human to pick a winner, with nothing recording which one to keep. `.github/renovate.json` extended a shared config, so Renovate was enabled by this repository rather than in spite of it. It is now `enabled: false` and kept rather than deleted, because with no config at all Renovate falls back to its own defaults and starts again. Dependabot was never configured, so it ran on defaults and found `node_modules.partial/` in some historical state of the repository - a path that is not on main and is not tracked. It has been proposing bumps to a vendored transitive package's manifest since August; nothing consumes them. `.github/dependabot.yml` now names `/` explicitly with `open-pull-requests-limit: 0`, which is the documented way to stop version updates while leaving security advisories alone. The same policy was inverted in the scaffold. `defaults/vcs/github` shipped a `renovate.json` and no buddy-bot workflow, so every generated app was opted into the bot the framework does not use and given none of the one it does. That is replaced by an app-shaped `buddy-bot.yml` - the three scheduled jobs and the manual trigger, without the framework's release plumbing. buddy-bot reads `config/buddy-bot.ts`, and `repository.owner`/`name` are not optional to it. The framework's copy names stacksjs/stacks, so a generated app inherited a bot aimed at this repository, which it has no token for - every run would have failed. It now has a scaffold template alongside cloud/dns/email/team, rendering the app's own slug and taking the owner from GITHUB_REPOSITORY_OWNER, which is already correct in Actions. While in the file: the template's pantry action was pinned at v0.10.47, so an app scaffolded today started nine months behind. Bumped to v0.11.57 to match this repository. Guarded by three tests, each verified to fail without its fix: the template ships a buddy-bot workflow, it ships config for no other dependency bot (a property, so the next bot's config is caught too), and the config template it reads is pointed at the app rather than at stacksjs/stacks.
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.
This PR contains the following updates:
=8->10.6.0Release Notes
mozilla/web-ext (web-ext)
=8 -> 10.6.0
Compare Source
A command line tool to help build, run, and test web extensions
📖 View Release Notes
🔗 View Changelog
Release Notes
Changelog
📊 Package Statistics
Configuration
📅 Schedule: 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 is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Buddy 🤖