-
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
Backmerge is incompatible with semantic-release v22 #57
Comments
I confirm, we have the same problem |
I restricted the dependencies to disallow using it with v22 for now. |
Thanks a lot @saitho. Could you trigger a new Release with your change from yesterday? My current workaround: {
...
"devDependencies": {
...
"@saithodev/semantic-release-backmerge": "3.2.0",
"semantic-release": "21.1.2",
...
},
...
"resolutions": {
"semantic-release": "21.1.2"
},
...
} |
Oh right, the build failed. Fixed and new version is released. |
Is there an existing issue for this?
Current Behavior
After upgrading to
semantic-release
v22, I am getting the following console output:Expected Behavior
It should work 😛
Steps To Reproduce
semantic-release
v22 and this packageEnvironment
Anything else?
The problem is, that the commit semantic-release/semantic-release@72ab317 introduced the
exports
property in thepackage.json
which makes it impossible to import internal files of the package. There is also already an issue discussing this issue on the semantic-release repo: semantic-release/semantic-release#2968.I just wanted to drop the info here if anybody else is experiencing this issue. But also to be aware of any possible fix discussed in the linked issue of the semantic-release repo.
The text was updated successfully, but these errors were encountered: