Skip to content

chore: bump bub to 0.5.1 and keep existing config in onboarding - #81

Merged
frostming merged 1 commit into
mainfrom
chore/bump-bub-0.5.1
Oct 11, 2026
Merged

frostming merged 1 commit into
mainfrom
chore/bump-bub-0.5.1

Conversation

@frostming

Copy link
Copy Markdown
Contributor

Summary

  • Bump the locked bub revision to the 0.5.1 release (06aadff). The previously locked commit was already its ancestor; the only difference is a website change.
  • bub 0.5.1 passes the loaded configuration to onboard_config and supports bub onboard <plugin> to reconfigure a single plugin (feat: support onboarding individual plugins with existing config bub#337). Channel plugins now reuse the existing config instead of wiping it:
    • dingtalk / discord / feishu: text and select prompts are prefilled from the current config.
    • all channel plugins (dingtalk, discord, feishu, qq, wecom): an empty secret answer keeps the existing secret.
  • Add regression tests: accepting every default with empty secrets returns the existing config unchanged.

Not changed

Test plan

  • uv run --frozen --group test pytest (694 passed, 3 skipped)
  • ruff check packages

🤖 Generated with Claude Code

bub 0.5.1 passes the loaded configuration to `onboard_config` and lets
`bub onboard <plugin>` reconfigure a single plugin (bubbuild/bub#337).
Prefill the dingtalk, discord and feishu prompts from the current
config, and keep existing secrets for all channel plugins when the
answer is left empty, so re-running onboarding no longer wipes values.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@frostming
frostming merged commit 1665dc3 into main Oct 11, 2026
1 check passed
@frostming
frostming deleted the chore/bump-bub-0.5.1 branch October 11, 2026 12:14
WZhongyun added a commit to WZhongyun/bub-contrib that referenced this pull request Oct 12, 2026
Bub 0.5.1 is released with the `exposure` option (bubbuild/bub#347), and
upstream migrated bub-qq to it (bubbuild#79) and kept the secret on re-onboarding
(bubbuild#81). Align with upstream's policy of following Bub's latest releases
while keeping a floor:

- Require bub>=0.5.1 with no upper bound; register qq.version with
  exposure="command" directly and drop the agent_use compatibility layer.
- Check the Bub version when the plugin module loads (bub_version.py),
  before importing modules that use newer interfaces, so an older Bub fails
  to load the plugin with the reason ("needs Bub >= 0.5.1") rather than an
  unknown keyword argument. Newer minor series load with a qq.bub.untested
  warning (their new tools stay admin-only under the Guard's allowlist),
  and development builds with qq.bub.prerelease.
- Resolve README and plugin.py conflicts, keeping both sides' changes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant