fix: upgrade semantic-release to 22 and add esm support (# #62
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.
Hi, I ran into this bug: #52 and it is most likely because of the full esm switch to native ES Modules here: semantic-release/semantic-release#2133
I think the solution is to make sure that this repo is compatible with v22, and switch from common js
require()
to ESM dynamicimport()
.However, I don't really see this PR as ideal, because the bundle types for
semantic-release
does not exportContext
anymore, so if you think that it seems a bit hacky with the way I've used@types/semantic-release
, I fully agree.I hope this could be of any help!
Update: We've tested and confirmed that this is indeed fixing #52, at least for our team.
Semantic Release Logs before and after testing this PR
Logs when encountering #52 :
Output codfish/semantic-release-action using require
Logs showing PR working
Output codfish/semantic-release-action using require/ESNext