Skip to content
This repository has been archived by the owner on Apr 24, 2024. It is now read-only.

Prepare for v0.2.0 npm publish #17

Merged
merged 1 commit into from
Nov 20, 2023
Merged

Prepare for v0.2.0 npm publish #17

merged 1 commit into from
Nov 20, 2023

Conversation

ameba23
Copy link
Contributor

@ameba23 ameba23 commented Nov 8, 2023

This just bumps the minor version and rebuilds for nodejs

Copy link

vercel bot commented Nov 8, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
x25519-chacha20poly1305 ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 8, 2023 2:36pm

@@ -4,7 +4,7 @@
"John Sahhar <[email protected]>"
],
"description": "x25519 & chacha20poly1305",
"version": "0.1.0",
"version": "0.2.0",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

https://semver.org/

dumb question: would this be a patch?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah i wasn't sure, i think its sort of grey area. In some cases encrypt_and_sign will give different output than before, because it used to give a uint8array containing the word 'failed' on failure, now it throws an error.

@benschac
Copy link
Contributor

small nit: merge if it's not relevent. LGTM.

outside of scope: would be cool if we added something like changesets https://github.com/changesets/changesets would be cool.

@benschac benschac self-requested a review November 15, 2023 13:41
@ameba23 ameba23 merged commit 29d1bde into main Nov 20, 2023
4 checks passed
@ameba23 ameba23 deleted the v0.2.0 branch November 20, 2023 07:43
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants