Conversation
* fix: require both key files to consider keypair present * fix: validate required arguments in set/get/delete * fix: create keypair directory recursively * fix: pin RSA padding to OAEP-SHA1 explicitly Node's default is OAEP-SHA1 today; pinning it guards against a future default change silently breaking existing .enc files. A switch to SHA-256 is reserved for v3.0.0 when the on-disk format changes anyway. * fix: write private key with 0600 permissions * fix: replace process.env.PWD with process.cwd() for portability * feat: add .env to project .gitignore on init * ci: run lint/build/test on pull requests * ci: replace npm-publish with release pipeline driven by package.json * docs: changelog entry for v2.3.0 * chore: bump version to 2.3.0 * style: apply prettier formatting
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Merging
developintomainships v2.3.0.The new
release.ymlworkflow (added in this release) will trigger on this push tomain, readversionfrompackage.json(2.3.0), tagv2.3.0, create the GitHub Release with notes extracted fromCHANGELOG.md, and publish to npm.See PR #7 for the full change set.