Add scope input for scoped Composer dependencies (#309)

[srtfisher]

Adds release-time support for scoped Composer dependencies, unblocking the require-pruning step that was previously commented out citing alleyinteractive/create-wordpress-plugin#309.

Pairs with alleyinteractive/create-wordpress-plugin#537, which adds the opt-in scoping machinery (.scoper/, composer scope) to the plugin template.

What

New scope input (default false, fully backward compatible). When scope: true:

1. Composer installs with dev dependencies (so php-scoper is available) instead of --no-dev.
2. Runs composer scope, which prefixes runtime dependencies into vendor-prefixed/.
3. Prunes require/require-dev from composer.json so the released artifact doesn't re-resolve (and re-conflict) dependencies when installed.

The prefixed vendor-prefixed/ directory is what ships; the plugin's .deployignore excludes vendor/, so dev dependencies installed in step 1 are never committed to the built branch.

When scope is false (the default), behaviour is unchanged: the existing --no-dev install runs and nothing is pruned.

Usage

A scoped plugin's built-release.yml opts in:

- uses: alleyinteractive/action-release@develop
  with:
    scope: true

Notes

• YAML validated.
• Behavioural verification depends on a downstream scoped plugin (create-wordpress-plugin#537); recommend testing together against a scoped fixture before merge.

🤖 Generated with Claude Code