feat: package version management with Changeset

[fazzaamiarso]

feat: package version management with Changeset

fix #225

Description of changes:

• install changeset cli
• add changeset github action

Tag a reviewer: @ayoayco

Tasks:

• I have ran the build command to make sure apps are working: npm run build
• I have ran the tests to make sure nothing is broken: npm run test
• I have ran the linter to make sure code is clean: npm run lint
• I have reviewed my own code to remove changes that are not needed

[netlify]

✅ Deploy Preview for astro-reactive ready!

Name	Link
🔨 Latest commit	421aaa7
🔍 Latest deploy log	https://app.netlify.com/sites/astro-reactive/deploys/63dbdcb1c89d3d0008f02f07
😎 Deploy Preview	https://deploy-preview-250--astro-reactive.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[netlify]

✅ Deploy Preview for astro-reactive-docs ready!

Name	Link
🔨 Latest commit	421aaa7
🔍 Latest deploy log	https://app.netlify.com/sites/astro-reactive-docs/deploys/63dbdcb1960f710008234373
😎 Deploy Preview	https://deploy-preview-250--astro-reactive-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[fazzaamiarso]

@ayoayco I think changeset is great for version management in monorepo. Although, we must read the docs quite a bit to understand. But, it definitely improves the workflow.

I will start to add changeset bot and github action to automate. It will look something like this PR once setup.

[ayoayco]

@fazzaamiarso Very interested in this. Looks like it will save us a lot of manual work. 🙏

[fazzaamiarso]

@ayoayco do you want to try implement changeset manually before adding automation? So, we can get familiar with the commands beforehand.

Manual changeset workflow should be similar to our usual versioning and publishing workflow.

[ayoayco]

@fazzaamiarso Yup! Does this branch have working changeset cli?

[fazzaamiarso]

Yes, it's working. It also comes with Github action that automatically creates a versioning PR.

I suggest to read the docs. Here are some useful parts.

• release beta, experimental, etc.
• cli option
• quickstart
• some faq

[ayoayco]

@fazzaamiarso Played around with changesets. Can you resolve conflicts so we can merge this? I want to test further the GH Actions. :)

[ayoayco]

This looks great to merge now, I think you just need to update the package lock ;)

[ayoayco]

Ah no worries, it was easy. I updated the package lock.

[ayoayco]

We're now getting a weird CI error regarding turbo not being found for this branch. Found a discussion and their resolution was this could be a caching issue, but our current CI does not have any caches 🤔 vercel/turbo#824

[fazzaamiarso]

Hey @ayoayco Sorry I've been very busy this time around, will get back at you this week.

[ayoayco]

Hey, no worries! Could you pick it up when you have the time? @fazzaamiarso

[fazzaamiarso]

@ayoayco I'm checking it now

[ayoayco]

@fazzaamiarso 👍 - I tried some changes but really couldn't make the CI error go away. Was wondering if it's just cached, but after deleting our GH Action caches still there 🤔

[fazzaamiarso]

@ayoayco I moved the PR to #261. It seems the package-lock conflict is the problem. I fresh installed changeset from the recent main branch and it worked.

[ayoayco]

Closing this one then