Update the actions in the release and issue workflows - #50
Merged
Conversation
release.yml runs on a tag and issue-flood on an issue, so neither is exercised here; release-drafter fires on the next push to main and is the one that gets checked immediately. Split off from the ci and docs bumps so a failure here cannot be mistaken for one there.
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
1 participant
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.
Second half of #48.
These workflows do not run on a pull request: release.yml fires on a tag, issue-flood on an issue. release-drafter runs on the next push to main, so it is verified within minutes of merging; the release path is not, and the first tag after this is the moment to watch.
The bumps are all major: upload-artifact v4 to v7, download-artifact v4 to v8, github-script v7 to v9, release-drafter v6 to v7.