Draft
Conversation
|
@vincentsarago Assuming I understand how you do releases correctly :) This would theoretically solve the issue, but it's still an open task. In the meantime, maybe make a group for each ecosystem to ensure you only get 1 PR per ecosystem and then set the prefix so that you only do a fix/patch bump? It could still be three versions, but at least what changed in each one is clear. |
Member
Author
Yes I should do this 🙏 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR aims to add Dependabot to automatically open PR to update runtimes.
I think we would need to customize commit message so it does release.
I'm not 💯 convince about this workflow though because we have 3 diff Dependabot which could in theory open 3 different PR so each merge could create 3 diff releases 😬