Publish to npm automatically after merging to main branch

[garethbowen]

Description

Automate the release process so that every time a commit with a changeset is merged to main and CI passes the code is published to npm. Changes without changesets should be chores that do not modify the code in any way.

Most of this work is already done by the release.yml action but we need to...

1. Generate and commit the release notes automatically. This will require additional permissions to be able to commit back to the repo.
2. Trigger the release action after build instead of on tag. Basically it should be a line item in the ci.yml workflow that depends on the success of all the other steps. Make sure this is triggered from node 24+ because otherwise the trusted publisher code won't work.

We don't need to worry about creating the git tag because the changesets release command already does that.

User Stories

• As a developer,
  I want releases to happen automatically,
  so that building is reliable and zero effort.

---

Related Issues