-
Notifications
You must be signed in to change notification settings - Fork 248
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
🔧 Repository: Renovate changesets on devDependencies
#942
Comments
I'd like to take a look at this, can I be assigned to the issue? |
Hey @04kash, thanks - assigned |
Opened a PR for this issue here: backstage/actions#159 |
I'm not sure about this as in some cases a changeset might be required even for devDependencies bumps. |
I think for cases where a changeset for devDependencies is needed, they could be manually added to the Renovate PR. WDYT @vinzscam ? |
I also noticed that in this repo we seem to be using this script: https://github.com/backstage/community-plugins/blob/main/scripts/ci/generate-bump-changesets.js rather than the action mentioned in the issue for genrating renovate changesets. So I'd assume we need to make changes to the script instead? |
but this will add more work as we need to identify whether a dependency bump should be added, with all the risks mentioned in
what's a good advantage of skipping changesets for |
📜 Description
The renovate-changeset action is adding changesets for changes that are only
devDependencies
. When we merge these changes it then kicks off the version packages which we don't need in this case as the package hans't actually changedThis is properly not something that we fix in this repo but here: https://github.com/backstage/actions/tree/main/renovate-changesets, logging it here for visibility and so I don't forget about it.
👍 Expected behavior
There should be not changesets if the changes are just related to
devDependencies
👎 Current Behavior
Changesets are added when there change is just for
devDependencies
👟 Reproduction steps
Example PR here: #877
📃 Provide the context for the Bug.
I merged this PR - #877 - which then triggers a bunch of Version Packages PRs.
👀 Have you spent some time to check if this bug has been raised before?
🏢 Have you read the Code of Conduct?
Are you willing to submit PR?
No, but I'm happy to collaborate on a PR with someone else
The text was updated successfully, but these errors were encountered: