Closed christian98 closed 11 months ago
I confirm, we have the same problem
I restricted the dependencies to disallow using it with v22 for now. I am not actively maintaining this plugin anymore, so I'd appreciate pull requests for any open issues.
I restricted the dependencies to disallow using it with v22 for now. I am not actively maintaining this plugin anymore, so I'd appreciate pull requests for any open issues.
Thanks a lot @saitho. Could you trigger a new Release with your change from yesterday?
My current workaround:
Add manual resolution of the semantic-release package to the package.json
and then recreate the lockfile.
Tested it with Yarn v1 and prevents it from installing semantic-release v22 as a dependency for @saithodev/semantic-release-backmerge.
{
...
"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 https://github.com/semantic-release/semantic-release/commit/72ab317bb0c6333c643f457f5658c318b78e4740 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: https://github.com/semantic-release/semantic-release/issues/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.