Open zoran995 opened 7 months ago
This is really very unexpected behavior for me, as someone who just started migrating all repositories: 6 nest.js and vue.js applications and 5 packages for them.
Before that I used semantic-release library in github action for each of the repositories and was happy, here I was expecting to see something similar, but I didn't find an adequate solution in the end.
It seems to me that the nx publish
command should have a --CI
option, which will automate all the processes described above, and replicate the semantic-release functionality at the expense of the nx functions
Hello, this is an issue for us because we're on gitlab so we can't set the github release option
Here's the relevant snippet : https://github.com/nrwl/nx/blob/master/packages/nx/src/command-line/release/release.ts#L205-L225
Seems like the gitPush()
could be lifted outside the condition of checking if you should create a workspace release (if (shouldCreateWorkspaceRelease && changelogResult.workspaceChangelog)
)
Are you accepting PRs regarding this issue ?
Same problem here.
Same here πͺ
Do you happen to have any news on this? This is a must, and it seems it's not working for some months π Can you please fix this? Thanks in advance
Any updates regarding this issue? Thanks
Current Behavior
When running
nx release
in ci without creating a new github release nx won't push the changes to source-control meaning the version change won't be reflected in repo/projectpackage.json
, and the commit won't be properly tagged in a git. On subsequent runs ofnx release
it will try to publish the same version again but it won't be able to overwrite the version on npm. This leads to an entirely broken CI process for us as it is not possible to release new versions, as a workaround we can addgit push
andgit push --tags
but that isn't written anywhere in the documentation. Only place mentioning pushing changes is next to the changelog configIf we set
"createRelease": "github"
it will push the changes to repo but that works only with githubExpected Behavior
After nx release is run and the new version is generated changes should be pushed to the source control and it should matter if we configured it to generate a changelog or GitHub release, of course, those should be grouped in one commit but the one shouldn't have to think if something is going to break since version change and the tag wasn't pushed to the source control.
Also, I would argue that there shouldn't be a need to configure the user name and email for git, but that should be handled through configuration and set up on ci if not defined already
GitHub Repo
No response
Steps to Reproduce
feat: configure ci
chore(release): 1.1.0 [skip ci]
Nx Report
Failure Logs
Package Manager Version
No response
Operating System
Additional Information
No response