Skip to content

Conversation

@TimoGlastra
Copy link
Contributor

Publishing failed @genaris :(

@TimoGlastra TimoGlastra requested a review from a team as a code owner January 5, 2026 16:22
@changeset-bot
Copy link

changeset-bot bot commented Jan 5, 2026

⚠️ No Changeset found

Latest commit: 539be5d

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

@TimoGlastra
Copy link
Contributor Author

We should wait with the publishing, there's an issue with the new wrapper. Somehow not catched in these tests or Credo, but when using it directly in a Node.JS proejct I get segmentation fault errors

[1]    48249 segmentation fault  node index.js

@genaris
Copy link
Contributor

genaris commented Jan 8, 2026

We should wait with the publishing, there's an issue with the new wrapper. Somehow not catched in these tests or Credo, but when using it directly in a Node.JS proejct I get segmentation fault errors

[1]    48249 segmentation fault  node index.js

Oh that's sad!

@TimoGlastra
Copy link
Contributor Author

If needed we can move this to a separate branch and cherry pick some changes to main.

As the updated registration would be nice to release

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.

3 participants