Skip to content
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

Closed
1 task done
EinfachHans opened this issue Jan 11, 2023 · 2 comments · Fixed by #40
Closed
1 task done

bug: fails with latest semantic-release version #38

EinfachHans opened this issue Jan 11, 2023 · 2 comments · Fixed by #40
Labels
bug Something isn't working released

Comments

@EinfachHans
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

Just received this error:

[8:42:47 AM] [semantic-release] [@saithodev/semantic-release-backmerge] › ✘  Error [ERR_REQUIRE_ESM]: require() of ES Module /Users/runner/work/xxx/node_modules/semantic-release/lib/get-git-auth-url.js from /Users/runner/work/xxx/node_modules/@saithodev/semantic-release-backmerge/dist/perform-backmerge.js not supported. 
[282](https://github.com/xxx/actions/runs/3890965311/jobs/6640863500#step:7:283)
Instead change the require of get-git-auth-url.js in /Users/runner/work/xxx/node_modules/@saithodev/semantic-release-backmerge/dist/perform-backmerge.js to a dynamic import() which is available in all CommonJS modules.
[283](https://github.com/xxx/actions/runs/3890965311/jobs/6640863500#step:7:284)
    at /Users/runner/work/xxx/node_modules/@saithodev/semantic-release-backmerge/dist/perform-backmerge.js:73:31
[284](https://github.com/xxx/actions/runs/3890965311/jobs/6640863500#step:7:285)
    at Generator.next (<anonymous>)
[285](https://github.com/xxx/actions/runs/3890965311/jobs/6640863500#step:7:286)
    at fulfilled (/Users/runner/work/xxx/node_modules/@saithodev/semantic-release-backmerge/dist/perform-backmerge.js:5:58)
[286](https://github.com/xxx/actions/runs/3890965311/jobs/6640863500#step:7:287)
Error: Process completed with exit code 1.

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

- **semantic-release/semantic-release** version: 20.0.2
- **@saithodev/semantic-release-backmerge** version: 2.1.2

Anything else?

No response

@EinfachHans EinfachHans added the bug Something isn't working label Jan 11, 2023
@EinfachHans EinfachHans changed the title <title> bug: fails with latest semantic-release version Jan 11, 2023
@saitho saitho pinned this issue Jan 11, 2023
@saitho
Copy link
Owner

saitho commented Jan 11, 2023

Thanks for the report. I'll take a look at it.
For now I published a bugfix release that prevents installing this plugin with semantic-release v20.

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.
@saitho
Copy link
Owner

saitho commented Feb 12, 2023

🎉 This issue has been resolved in version 3.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@saitho saitho unpinned this issue Feb 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working released
Projects
None yet
2 participants