The mach-composer/pnpm-dependencies-action can be used to render a string containing --git-filter-path ... arguments needed for the mach-composer/new-component-version-action within a monorepo context.
In order for that action to generate a good list of changes made to a component it needs to be aware of the dependencies within the monorepo. Any change in a dependency could trigger a new component version and must be part of the changelog.
By providing a full list of --get-filter-path arguments for each dependency we ensure all related commits are part of the output.
where service-name could be catalog for example.
- uses: mach-composer/pnpm-dependencies-action@v1
id: filter-paths
with:
package: "@commerce-backend/${{ inputs.service-name }}"
- name: Mach Composer Cloud - Register version
uses: mach-composer/[email protected]
with:
organization: my-org
project: my-mach-project
component: ${{ inputs.service-name }}
client_id: ${{ secrets.MCC_CLIENT_ID }}
client_secret: ${{ secrets.MCC_CLIENT_SECRET }}
args: --verbose --git-filter-path backend/services/${{ inputs.service-name }} ${{ steps.filter-paths.outputs.paths }}Some improvements can be made to this action;
- Instead of outputting a string like
--git-filter-path backend/packages/graphql-types --git-filter-path backend/packages/cache-utils --git-filter-path /packages/observabilityinstead it should output an array of strings;["backend/packages/graphql-types", "backend/packages/cache-utils", "/packages/observability"]so it can be used for more purposes as well.