Add changesets tool setup to mint-components#459
Conversation
Co-authored-by: noahwc <7761715+noahwc@users.noreply.github.com>
Noah Clarke (noahwc)
requested review from
AndiLuo,
Jayden Chan (jayden-chan) and
Zach Harrison (zachharrison)
There was a problem hiding this comment.
Pull request overview
This PR adds the changesets tool to the mint-components package to automate version management and changelog generation. The setup includes configuration files, npm scripts for creating changesets and publishing releases, and a GitHub Actions workflow to automate the release process when changes are merged to main.
Key Changes:
- Added changesets dependencies and configuration
- Created npm scripts for version management workflow
- Added GitHub Actions workflow for automated releases
- Documented the changeset workflow in the README
Reviewed changes
Copilot reviewed 5 out of 6 changed files in this pull request and generated 5 comments.
Show a summary per file
| File | Description |
|---|---|
| packages/mint-components/package.json | Added changesets dependencies and npm scripts for managing versions and releases |
| packages/mint-components/.changeset/config.json | Configured changesets with GitHub changelog integration and baseBranch set to "master" |
| packages/mint-components/.changeset/README.md | Auto-generated documentation about using changesets |
| packages/mint-components/readme.md | Added comprehensive documentation about the changeset workflow and release process |
| .github/workflows/mint-components-merge-to-main.yml | Created GitHub Actions workflow to automate version bumps and npm publishing |
Files not reviewed (1)
- packages/mint-components/package-lock.json: Language not supported
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 5 out of 6 changed files in this pull request and generated 7 comments.
Files not reviewed (1)
- packages/mint-components/package-lock.json: Language not supported
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
Jayden Chan (@jayden-chan), wondering if we want to reconcile this with the current |
None of the features in changesets are necessary for those packages, so in my opinion it's definitely not worth adding another external dependency and increasing our attack surface area just for the sake of consistency. If you want to take on the responsibility of implementing and maintaining changesets for those packages then you are welcome to, but I do not see the value and most likely won't be doing it myself. |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 7 out of 8 changed files in this pull request and generated 5 comments.
Files not reviewed (1)
- packages/mint-components/package-lock.json: Language not supported
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <copilot@github.com>
Co-authored-by: Copilot <copilot@github.com>
|
|
||
| - name: Create release pull request or publish to npm | ||
| id: changesets | ||
| uses: changesets/action@v1 |
There was a problem hiding this comment.
Pin this to a full length SHA.
Co-authored-by: Jayden Chan <32287958+jayden-chan@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 8 out of 9 changed files in this pull request and generated 4 comments.
Files not reviewed (1)
- packages/mint-components/package-lock.json: Language not supported
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <copilot@github.com>
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 8 out of 9 changed files in this pull request and generated 2 comments.
Files not reviewed (1)
- packages/mint-components/package-lock.json: Language not supported
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| - name: Create release pull request or publish to npm | ||
| id: changesets | ||
| uses: changesets/action@6a0a831ff30acef54f2c6aa1cbbc1096b066edaf # 6a0a8 = v1.7.0 | ||
| with: | ||
| version: cd packages/mint-components && npm run version | ||
| publish: cd packages/mint-components && npm run release | ||
| title: "mint-components - Version Packages" |
| "postinstall": "patch-package", | ||
| "prepack": "npm run build", | ||
| "changeset": "changeset", | ||
| "version": "changeset version && npm install", |
Co-authored-by: Copilot <copilot@github.com>
Overview
This PR adds and configures the changesets tool to the
packages/mint-componentspackage to streamline version management and changelog generation.Changes
Dependencies
@changesets/cli(v2.29.7) as a dev dependencyConfiguration
.changesetdirectory with configuration files:config.json: Configured for public npm package publishing withmasteras the base branchREADME.md: Auto-generated documentation about using changesetsScripts
Added three npm scripts for managing releases:
npm run changeset- Create a new changeset interactivelynpm run version- Apply changesets and update package version/CHANGELOGnpm run release- Publish the package to npmUsage
When making changes to mint-components:
Create a changeset to document your changes:
This prompts you to select the change type (patch/minor/major) and provide a summary.
Version the package when ready to release:
This consumes all pending changesets and updates
package.jsonandCHANGELOG.md.Publish to npm:
Benefits
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
googlechromelabs.github.ionode install.mjs(dns block)https://storage.googleapis.com/chrome-for-testing-public/125.0.6422.78/linux64/chrome-headless-shell-linux64.zipnode install.mjs(http block)If you need me to access, download, or install something from one of these locations, you can either:
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.