Disable Plugin Guide by default - #2587
Merged
SawyerHood merged 1 commit intoAug 27, 2026
Merged
Conversation
SawyerHood
deleted the
bb/disable-plugin-guide-by-default-thr_iairm6hh2j
branch
August 27, 2026 19:48
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.
Human comments
What was wrong
The built-in plugin registry enabled the Plugin Guide on each fresh database. This made a developer tool run before the user chose it.
What changed
The Plugin Guide now installs in the disabled state on a fresh database. Existing databases keep their saved choice. The package smoke test no longer expects this plugin to run by default.
How you verified
pnpm exec turbo run test --filter=@bb/server -- test/services/plugins/builtin-plugins.test.ts.pnpm exec turbo run typecheck --filter=@bb/server.node --check packages/bb-app/scripts/smoke-tarball.mjs.git diff --check.