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
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Reason: Some updates require changesets. Simple as that, I have it set right now that only devDependencies will get auto merged, and non-major changes.
So if we update a dependency that may require a changeset.
For example: #22 probably requires a changeset, since its a "dependency upgrade" (if we wanted to merge it).
Caveat: I do not see this working for pnpm catalogs.
basically the catalog defines a range, and then renovate mostly just updates the lockfile. So this is probably fine since we aren't actually changing the version range within the package.
If we do, we would do it manually in the pnpm-workspace file and then make our own changeset.
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ryanbas21
force-pushed
the
renovate/reconfigure
branch
from
Groups renovate dependencies so theres less noise. add nx to ignore pattern since we do that with
nx.Unfortunately, the
ignorepattern is exact match only and not globadds a GH action that will add changesets for the deps when they are needed. uses https://www.npmjs.com/package/@scaleway/changesets-renovate
Which is seen here: https://github.com/scaleway/scaleway-lib/blob/94fd991db6ac46ea034d486837e4ca4dbc38d8c3/.github/workflows/changesets-renovate.yml
Which I looked at how some of these actions are run here: scaleway/scaleway-lib#2402
Reason: Some updates require changesets. Simple as that, I have it set right now that only devDependencies will get auto merged, and non-major changes.
So if we update a
dependencythat may require a changeset.For example: #22 probably requires a changeset, since its a "dependency upgrade" (if we wanted to merge it).
Caveat: I do not see this working for
pnpm catalogs.basically the catalog defines a range, and then renovate mostly just updates the lockfile. So this is probably fine since we aren't actually changing the version range within the package.
If we do, we would do it manually in the
pnpm-workspacefile and then make our own changeset.