Skip to content

Conversation

@github-actions
Copy link
Contributor

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

@hyperledger/anoncreds-nodejs@0.3.4

Patch Changes

  • aa9f0d2: update to use anoncreds-rs v0.2.3
    • @hyperledger/anoncreds-shared@0.3.4

@hyperledger/anoncreds-react-native@0.3.4

Patch Changes

  • aa9f0d2: update to use anoncreds-rs v0.2.3
    • @hyperledger/anoncreds-shared@0.3.4

@hyperledger/anoncreds-shared@0.3.4

Signed-off-by: "github-actions[bot]" <"41898282+github-actions[bot]@users.noreply.github.com">
@github-actions github-actions bot force-pushed the changeset-release/main branch from 7866973 to b5afb10 Compare November 14, 2025 20:06
@TimoGlastra TimoGlastra merged commit 78c54e5 into main Nov 14, 2025
12 checks passed
@TimoGlastra TimoGlastra deleted the changeset-release/main branch November 14, 2025 20:25
@swcurran
Copy link
Contributor

I'm not clear if a release was completed. In the tags, there is no 0.3.4 -- just Alphas of 0.3.4. And now there are Alphas of 0.3.5. How do we get a properly tagged release?

@TimoGlastra
Copy link
Contributor

Yeah there's a weird bug with the releases. We have this in almost all our repositories. First it created two releases, and now it creates none

@TimoGlastra
Copy link
Contributor

I created a manual release for now. It was already published on NPM.

https://github.com/hyperledger/anoncreds-wrapper-javascript/releases/tag/v0.3.4

@swcurran
Copy link
Contributor

Thanks @TimoGlastra

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