Conversation
68dc550 to
4fecddf
Compare
|
I merged #39 as part of testing our release automation. I was expecting this PR to be updated because it says "whenever you add more changesets to main, this PR will be updated." but it hasn't yet. Will check back in the morning in case its held up somewhere - but more likely I just need to get up to speed with how Changesets work :) |
4fecddf to
e0266a7
Compare
|
For whatever reason, this PR did not get automatically updated with the new changeset, so I ran the release.yml workflow manually, gh workflow run release.yml --ref mainand this caused the above,
So, will merge this now with the expectation that releases are made of new versions of all packages. |
|
Nope, did not release packages. Testing this automation was the reason for creating #39. Need to revisit release pipeline. |
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
oxa-types@0.2.0
Minor Changes
7a00e13Thanks @nokome! - Add Emphasis node type@oxa/core@0.1.1
Patch Changes
#37
7f4407cThanks @rowanc1! - Export version statically rather than dynamicallyUpdated dependencies [
7a00e13]:oxa@0.1.1