-
Notifications
You must be signed in to change notification settings - Fork 10
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
bug: fails with latest semantic-release version #38
Comments
Thanks for the report. I'll take a look at it. |
saitho
added a commit
that referenced
this issue
Jan 13, 2023
Import semantic-release functions via ESM. Fixes: #38
saitho
added a commit
that referenced
this issue
Jan 13, 2023
Import semantic-release functions via ESM. Fixes: #38
saitho
added a commit
that referenced
this issue
Feb 1, 2023
Import semantic-release functions via ESM. Fixes: #38
saitho
added a commit
that referenced
this issue
Feb 7, 2023
Import semantic-release functions via ESM. Fixes: #38
saitho
added a commit
that referenced
this issue
Feb 7, 2023
Import semantic-release functions via ESM. Fixes: #38
saitho
added a commit
that referenced
this issue
Feb 7, 2023
Import semantic-release functions via ESM. Fixes: #38
saitho
added a commit
that referenced
this issue
Feb 7, 2023
Import semantic-release functions via ESM. Fixes: #38
saitho
added a commit
that referenced
this issue
Feb 12, 2023
BREAKING CHANGE: Import semantic-release functions via ESM. Loses compatibility with semantic-release before v20. Fixes: #38
saitho
added a commit
that referenced
this issue
Feb 12, 2023
BREAKING CHANGE: Import semantic-release functions via ESM. Loses compatibility with semantic-release before v20. Fixes: #38
saitho
added a commit
that referenced
this issue
Feb 12, 2023
BREAKING CHANGE: Import semantic-release functions via ESM. Loses compatibility with semantic-release before v20. Fixes: #38
saitho
added a commit
that referenced
this issue
Feb 12, 2023
BREAKING CHANGE: Import semantic-release functions via ESM. Loses compatibility with semantic-release before v20. Fixes: #38
saitho
added a commit
that referenced
this issue
Feb 12, 2023
BREAKING CHANGE: Import semantic-release functions via ESM. Loses compatibility with semantic-release before v20. Fixes: #38
saitho
added a commit
that referenced
this issue
Feb 12, 2023
BREAKING CHANGE: Import semantic-release functions via ESM. Loses compatibility with semantic-release before v20. Fixes: #38
github-actions bot
pushed a commit
that referenced
this issue
Feb 12, 2023
# [3.0.0](v2.2.0...v3.0.0) (2023-02-12) ### Bug Fixes * Compatibility with semantic-release v20 ([d8b8332](d8b8332)), closes [#38](#38) ### Features * remove branchName setting ([7a5772d](7a5772d)) * rename branches to backmergeBranches ([f84713b](f84713b)) ### BREAKING CHANGES * Setting `branches` is renamed into `backmergeBranches` to avoid conflicts with the setting for semantic-release. * `branchName` setting is removed. Use `branches` instead. * Import semantic-release functions via ESM. Loses compatibility with semantic-release before v20.
🎉 This issue has been resolved in version 3.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Current Behavior
Just received this error:
Probably relevant to breaking change in 20.0.0 that semantic release is now ESM-only
Expected Behavior
It should work with 20.0.0
Steps To Reproduce
Use this plugin with the latest semantic-release version
Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: