Repository navigation
ci: Reuse the open plugin catalog PR for each plugin - #256
Merged
Merged
Conversation
Pin the shared update-plugin-index action at v1.22.0, which updates the open catalog PR for a plugin instead of opening one per release (datum-cloud/actions#98). Its inputs are unchanged.
3 of 4 tasks
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
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.
Summary
Each release opens a new plugin catalog PR in datum-cloud/datumctl-plugins and leaves the one before it open, so the bump PRs pile up unmerged and users install old plugins. Since v1.22.0 (datum-cloud/actions#98), the shared update-plugin-index action updates the open PR for the plugin instead, and this repository still pins v1.21.0.
update-plugin-index@v1.21.0to@v1.22.0concurrencygroup on the catalog job, one per catalog, plugin and base branchTest plan