You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have this configuration applied in the .release.json : [ "@semantic-release/npm", { "pkgRoot": "./dist" } ]
The package is being published with the content of the src instead of the dist as I indicate, this with semantic-release worked for me, as a temporary solution I had to add "files": ["dist"] in the package.json of the specific package but this makes it include the directory dist in the package, not just its content as before.
I got the same issue when using multi-semantic-release to publish the angular lib projects. The current workaround is to delete projects dir in the pipeline and copy dist/* dir to projects before running the semantic release.
I have this configuration applied in the .release.json :
[ "@semantic-release/npm", { "pkgRoot": "./dist" } ]
The package is being published with the content of the src instead of the dist as I indicate, this with semantic-release worked for me, as a temporary solution I had to add
"files": ["dist"]
in the package.json of the specific package but this makes it include the directory dist in the package, not just its content as before.npm: '9.5.0',
node: '18.15.0'
multi-semantic-release: '3.0.2'
The text was updated successfully, but these errors were encountered: