chore: modernize and migrate to esm #127
Merged
Conversation
This file contains 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
Closed
wolfy1339
reviewed
Jul 20, 2024
wolfy1339
reviewed
Jul 21, 2024
wolfy1339
reviewed
Jul 21, 2024
wolfy1339
reviewed
Jul 21, 2024
Co-authored-by: wolfy1339 <[email protected]>
wolfy1339
approved these changes
Jul 21, 2024
|
🎉 This issue has been resolved in version 2.0.0-beta.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
AaronDewes
pushed a commit
that referenced
this pull request
Aug 3, 2024
BREAKING CHANGE: This package is now ESM only. * feat: add support for PKCS8 keys (#129) Co-authored-by: Samuel El-Borai <[email protected]> * chore: modernize and migrate to esm (#127) Co-authored-by: wolfy1339 <[email protected]> --------- Co-authored-by: Samuel El-Borai <[email protected]> Co-authored-by: wolfy1339 <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
how can we ensure that we release next version as a major?
should we target a next branch?