Scope mint releases

[Noah Clarke (noahwc)]

Description of the change

Don't show mint-component releases as releases of the entire monorepo

Type of change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation or Development tools (readme, specs, tests, code formatting)

Links

• Jira issue number: (PUT IT HERE)
• Process.st launch checklist: (PUT IT HERE)

Checklists

Development

• Prettier was run (if applicable)
• The behaviour changes in the pull request are covered by specs
• All tests related to the changed code pass in development

Paperwork

• This pull request has a descriptive title and information useful to a reviewer
• This pull request has a Jira number
• This pull request has a Process.st launch checklist

Code review

• Changes have been reviewed by at least one other engineer
• Security impacts of this change have been considered

[Copilot]

Pull request overview

Scopes the mint-components release workflow so its GitHub Releases are tagged per-package (mint-components@x.y.z) rather than appearing as releases for the entire monorepo. The built-in release creation by changesets/action is disabled and replaced with a custom step that uses the publishedPackages output to create a properly scoped release.

Changes:

• Disable changesets/action's built-in GitHub Release creation via createGithubReleases: false.
• Add a new actions/github-script step that parses publishedPackages and calls repos.createRelease with a name@version tag, marking prereleases when the version contains -.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.