-
Notifications
You must be signed in to change notification settings - Fork 229
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
monorepo tags broken in v3 #457
Comments
I'm working on this issue with @wraithgar and I wanted to update this with a npx release-please release-pr \
--release-type=node --token=XXX --path=workspaces/arborist \
--monorepo-tags --package-name=@npmcli/arborist \
--component=arborist --repo-url=npm/cli (I'm not sure if the I got this command from this issue: googleapis/release-please#1132. The only difference I can see is that I am explicitly supplying the name instead of letting |
Here are some logs I collected that I haven't had a chance to look through fully yet: Release Please Action Logs
release-please cli logs
|
This allows for release-please to fallback to the deault value since it uses the nullish coalescing operator for that check. Fixes #457 Co-authored-by: Benjamin E. Coe <bencoe@google.com>
TL;DR
When we use v3 of this action our workspace PRs pick up the version from our root project, not the workspace.
Expected behavior
PRs for workspaces correctly find the current version from monorepo tags.
Observed behavior
The PR that is made uses the version from the root tag. Here is an erroneous PR that correctly makes the changelog for arborist (a workspace) but tags it as if the root project (npm itself) is the version arborist is on
https://github.com/npm/cli/pull/4648/files
Action YAML
Log output
No response
Additional information
If we downgrade to v2 in another repo that doesn't use workspaces, it is unable to see any of the releases v3 made.
If we pin to v3.0.0-v3.1.0, the pr it makes is always
v1.0.0
, it is in release-please-action v3.1.1 this behavior starts.The text was updated successfully, but these errors were encountered: