Skip to content

feat: ship user plugins in every build - #55

Merged
cu-e merged 1 commit into
devfrom
feat/user-plugins-by-default
Nov 10, 2026
Merged

cu-e merged 1 commit into
devfrom
feat/user-plugins-by-default

Conversation

@cu-e

@cu-e cu-e commented Nov 10, 2026

Copy link
Copy Markdown
Owner

The same change as the PR to master, for dev: the user-plugins feature is gone and user plugins ship in every build (ADR 0161).


Generated by Claude Code

Users could not install a plugin from a release: the user-plugin track was
compiled in only with --features nocterm/user-plugins, which no release
built. The feature is gone, and the plugin crates are ordinary dependencies.
A run still loads user plugins only when [plugins] user_plugins is on, and
--safe-mode loads none.

- 57 cfg gates and the placeholder module for builds without plugins are
  removed.
- The xtask compile-out rule and the release-pipeline check that kept the
  feature out of releases are removed. The test-only and banned feature
  rules remain.
- CI builds the example guest in Build and test and runs the workspace
  tests once against the real WASM guest; the separate user-plugin job and
  its clippy pass are gone.
- The notices now cover wasmi and wasmparser, with their original license
  files pinned in licensing/.

ADR 0161 records the decision.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WAgRyZqRCp4XuUHFDB1w3k
@cu-e
cu-e merged commit 52d94c5 into dev Nov 10, 2026
@cu-e
cu-e deleted the feat/user-plugins-by-default branch November 10, 2026 16:32
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.

2 participants