-
Notifications
You must be signed in to change notification settings - Fork 400
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
Not updating .release-please-manifest.json
#2172
Comments
I'm also seeing this issue and managed to reproduce locally with the CLI. If it'd be useful then I can try and push a reduced test case somewhere. I'm seeing it in both a brand new project and an existing one that I tried migrating to the latest version of Release Please. |
@rowanmanning please do, I would be happy to take a look myself if I have a repo. |
I'm also having the same issue with this. So I did some experiment and debugging on it. I reproduced this problem with several repos linked below.
Turned out this problem happened on 01Joseph-Hwang10/release-please-standalone-example#1 and 01Joseph-Hwang10/release-please-monorepo-without-root-example#1. Debugging on 01Joseph-Hwang10/release-please-standalone-example#1As I first faced this issue in standalone node project environment, I did some debugging in my local machine with What I ran: release-please release-pr --token="$GITHUB_TOKEN" --repo-url="https://github.com/01Joseph-Hwang10/release-please-standalone-example" --trace --dry-run The below was the output. Note that there exist several
|
The whole repo should be released as a single artifact but I want separate module folders for plugins with their own builds. Tying the version to just the server should be fine. Otherwise running into this googleapis/release-please#2172
Happens to me too with After debugging I can confirm it overwrites first update like @01Joseph-Hwang10 found out. |
I fixed this in above commit, take a look at config key |
Hey team, happening to us as well on a bare nodejs mono repo. Anything we can do on our side to help repro or fix the issue? Thanks |
This worked for me wheresrhys/fetch-mock#706 |
Sets `separate-pull-requests` explicitly to false. See googleapis/release-please#2172
Sets `separate-pull-requests` explicitly to false. See googleapis/release-please#2172
This also happens with |
I also add the same problem when trying to set Following the investigation done by @01Joseph-Hwang10 , I tried to find why some Manifest updaters are empty. As it turns out, the versionMap of the manifest is using the return of the buildUpdatedVersions method. But this method only adds 'candidates' to I managed to reproduce this behavior in the first commit of my PR: I'm adding new assertions that are verifying that the My proposal for fixing this is to modify the |
Ran into the same issue. Release please is not updating the My {
"bump-minor-pre-major": true,
"bump-patch-for-minor-pre-major": false,
"include-v-in-tag": true,
"separate-pull-requests": true,
"sequential-calls": true,
"packages": {
"packages/package1": {
"package-name": "package1",
"release-type": "node"
},
"packages/package2": {
"package-name": "package2",
"release-type": "node"
}
},
"plugins": [
{
"type": "node-workspace"
}
]
} |
We use
release-please
to create releases for the Puppeteer project. The current structure is a mono repo so we use a configuration file to express this.This works well for the 3 packages that depend on each other
puppeteer
,puppeteer-core
, and@puppeteer/browsers
.But for the last one
@puppeteer/ng-schematics
we are seeing issue that the release does not update.release-please-manifest.json
.This can be observed on the latest PR - puppeteer/puppeteer#11543.
If we do merge this PR without updating the manifest manually
release-please
will open a new one as the version differs with the manifest file. Observed:Initial - puppeteer/puppeteer#11496
A second one - puppeteer/puppeteer#11508
The issue is not consistent. It doesn't fail all the time as you can see from puppeteer/puppeteer#11488
Environment details
Steps to reproduce
The text was updated successfully, but these errors were encountered: