[ci] changeset based package publishing

[nickfrosty]

adding changeset based package publishing

Fixes: #148

[changeset-bot]

⚠️ No Changeset found

Latest commit: 58c150c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[nickfrosty]

@beeman this is ready for a first pass look. It should be good to go. If this is satisfactory, I will update the MAINTEINERS.md to reflect this. I would also recommend we remove the ci.yml script in favor of the PR one I added. Accomplishes the same task, but it uses a matrix of versions to test/lint on. Plus is inline with gill, kit, and wallet ui

[nickfrosty]

also worth considering: only running the test templates action when the the src dir or specific config files changes (like package json). This should prevent the excess runners when they are not needed

[beeman]

Great work @nickfrosty, thanks! 🙏

[beeman]

@beeman this is ready for a first pass look. It should be good to go. If this is satisfactory, I will update the MAINTEINERS.md to reflect this. I would also recommend we remove the ci.yml script in favor of the PR one I added. Accomplishes the same task, but it uses a matrix of versions to test/lint on. Plus is inline with gill, kit, and wallet ui

Looks all good to me so far!

Happy for you to update the MAINTAINERS file and remove the obsolete ci.yml.

Also created a follow-up issue #154 for optimizing the e2e-test so it'll test unrelated stuff faster.