Skip to content

refactor: migrate plugins config to top-level key#148

Open
outofcoffee wants to merge 1 commit into
developfrom
claude/nifty-turing-LS9Es
Open

refactor: migrate plugins config to top-level key#148
outofcoffee wants to merge 1 commit into
developfrom
claude/nifty-turing-LS9Es

Conversation

@outofcoffee
Copy link
Copy Markdown
Contributor

@outofcoffee outofcoffee commented Jun 4, 2026

Summary

This PR migrates the plugin configuration from the nested default.plugins key to a top-level plugins key while maintaining backward compatibility with existing configurations.

Key Changes

  • New top-level plugins config key: Plugins can now be configured at the root level of the config file instead of under default.plugins
  • Backward compatibility: The deprecated default.plugins key is still supported and will emit a deprecation warning when used
  • Automatic merging and deduplication: When both keys are present, plugins are merged and deduplicated to avoid installing the same plugin twice
  • Migration on write: When plugins are written back to the config file, they are stored using the new top-level key and the deprecated key is cleared
  • Updated documentation: Config examples in docs/config.md now show the new top-level plugins format

…lugins'

The plugin list can now be configured at the top level of .imposter.yaml
and config.yaml, which is simpler and more intuitive. The previous
nested 'default.plugins' key is still supported with a deprecation
warning.

https://claude.ai/code/session_01MUAgVQQU6HNuqnoKeMk33V
@outofcoffee outofcoffee changed the title Migrate plugins config to top-level key with backward compatibility refactor: migrate plugins config to top-level key with backward compatibility Jun 4, 2026
@outofcoffee outofcoffee changed the title refactor: migrate plugins config to top-level key with backward compatibility refactor: migrate plugins config to top-level key Jun 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants