Skip to content

Version Packages#38

Merged
nokome merged 1 commit intomainfrom
changeset-release/main
Jan 22, 2026
Merged

Version Packages#38
nokome merged 1 commit intomainfrom
changeset-release/main

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Dec 24, 2025

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

@oxa/core@0.1.1

Patch Changes

  • #37 7f4407c Thanks @rowanc1! - Export version statically rather than dynamically

  • Updated dependencies [7a00e13]:

    • oxa-types@0.2.0

oxa@0.1.1

@github-actions github-actions bot force-pushed the changeset-release/main branch from 68dc550 to 4fecddf Compare December 24, 2025 04:42
@nokome
Copy link
Collaborator

nokome commented Jan 21, 2026

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 :)

@github-actions github-actions bot force-pushed the changeset-release/main branch from 4fecddf to e0266a7 Compare January 22, 2026 02:51
@nokome
Copy link
Collaborator

nokome commented Jan 22, 2026

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 main

and this caused the above,

force-pushed the changeset-release/main branch from 4fecddf to e0266a7

So, will merge this now with the expectation that releases are made of new versions of all packages.

@nokome nokome merged commit e889507 into main Jan 22, 2026
@nokome nokome deleted the changeset-release/main branch January 22, 2026 02:59
@nokome
Copy link
Collaborator

nokome commented Jan 22, 2026

Nope, did not release packages. Testing this automation was the reason for creating #39. Need to revisit release pipeline.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant