Publish Solution action does not support targeting a specific solution (no solution-name input)

[wesco-prathapmotupalli]

Title

Publish Solution action (microsoft/powerplatform-actions/publish-solution@v1) does not support targeting a specific solution (no solution-name input)

Description

Problem

The publish-solution GitHub Action (action.yml) currently does not allow publishing customizations for a specific solution. There is no solution-name input; as a result, invoking the action publishes all customizations in the environment.

  authN to env. authType:SPN authScheme:; cloudInstance: Public; envUrl: https://XXX.crm.dynamics.com/
  '***' authenticated successfully.
  Validating connection...
  Connected to... CRM - Environment
  Default organization: CRM - Environment
  Authentication profile created
      * UNIVERSAL                                : ***     Public https://XXX.crm.dynamics.com/
  The Authentication Result: '***' authenticated successfully.,Validating connection...,Connected to... CRM - Environment,Default organization: CRM - Environment,Authentication profile created,    * UNIVERSAL                                : ***     Public https://XXX.crm.dynamics.com/,
  Calling pac cli inputs: solution publish --async false --max-async-wait-time 60
  Connected as ***
  Connected to... CRM - Environment
  Publishing All Customizations...
  Published All Customizations.
  PublishSolution Action Result: Connected as ***,Connected to... CRM - Environment,,Publishing All Customizations...,,Published All Customizations.
  Authentication profiles and token cache removed
  The Clear Authentication Result: Authentication profiles and token cache removed

Expected Behavior

There should be an option to specify a solution-name, so only the customizations for the named solution are published (similar to what is possible with the Power Platform CLI: pac solution publish --name <solution-name>).

Actual Behavior

All customizations for the environment are published. This can cause unintended changes and performance issues, especially in environments with multiple solutions.

Steps to Reproduce

1. Use the microsoft/powerplatform-actions/publish-solution@v1 action in a workflow.
2. Attempt to provide a solution name (not supported).
3. Observe that all customizations are published, not just those for a specific solution.

Impact

• Increases risk of deploying unwanted changes.
• Slows down deployment pipelines.
• Makes it difficult to follow best practices for solution lifecycle management.

Proposed Solution

• Add a solution-name input to the action, passing it to the underlying CLI command.
• If solution-name is provided, publish only that solution; otherwise, fall back to current behavior.

Reference

• action.yml
• Power Platform CLI - pac solution publish