New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ES Module #2543
Comments
travi
added a commit
that referenced
this issue
Aug 27, 2022
travi
added a commit
that referenced
this issue
Aug 27, 2022
travi
added a commit
that referenced
this issue
Aug 27, 2022
travi
added a commit
that referenced
this issue
Aug 27, 2022
travi
added a commit
that referenced
this issue
Sep 12, 2022
…oading plugins to isolate the conversion ahead of #2543
travi
added a commit
that referenced
this issue
Oct 7, 2022
…bleeding between tests we should try to adjust the stub setup in each test to try to avoid the need for this, but i think that should be tackled separately from the current esm effort for #2543
travi
added a commit
that referenced
this issue
Oct 7, 2022
i think the implementation should support loading of esm plugins as well, but we should add test coverage for those scenarios as a follow up for #2543
travi
added a commit
that referenced
this issue
Oct 7, 2022
i think the implementation should support loading of esm plugins as well, but we should add test coverage for those scenarios as a follow up for #2543
travi
added a commit
that referenced
this issue
Oct 7, 2022
travi
added a commit
that referenced
this issue
Oct 7, 2022
…malization BREAKING CHANGE: since semantic-release now executes in an ESM context, the file extension is required when referencing plugin files for #2543
travi
added a commit
that referenced
this issue
Oct 8, 2022
travi
added a commit
that referenced
this issue
Nov 4, 2022
travi
added a commit
that referenced
this issue
Nov 4, 2022
travi
added a commit
that referenced
this issue
Nov 4, 2022
since loading json config cannot be accomplished with import without import assertions for #2543
travi
added a commit
that referenced
this issue
Nov 5, 2022
travi
added a commit
that referenced
this issue
Nov 11, 2022
for #2543 BREAKING CHANGE: semantic-release is now ESM-only. since it is used through its own executable, the impact on consuming projects should be minimal BREAKING CHANGE: references to plugin files in configs need to include the file extension because of executing in an ESM context
This was referenced Nov 11, 2022
travi
added a commit
that referenced
this issue
Nov 19, 2022
in accordance with our node support policy: https://semantic-release.gitbook.io/semantic-release/support/node-support-policy BREAKING CHANGE: Node v18 or greater is now required. Please refer to https://semantic-release.gitbook.io/semantic-release/support/node-version for recommended options for releasing with a supported node version. for #2543
travi
added a commit
that referenced
this issue
Dec 6, 2022
travi
added a commit
that referenced
this issue
Dec 6, 2022
travi
added a commit
that referenced
this issue
Dec 7, 2022
the updates for core are complete as far as we know at this point, so we plan to promote the latest beta to stable very soon. if anyone is eager to try out the changes before we promote to latest, give the latest beta version a shot and let us know here if you find any problems. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Part of our efforts to migrate
semantic-release
to native ES Modules: #2133The text was updated successfully, but these errors were encountered: