Update workflow action versions #914
Merged
Conversation
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
jpreese
force-pushed
the
update-pr-workflow
branch
5 times, most recently
from
43177f1 to
e3de1e9
Compare
Signed-off-by: John Reese <[email protected]>
jpreese
force-pushed
the
update-pr-workflow
branch
from
e3de1e9 to
12ace0c
Compare
Signed-off-by: John Reese <[email protected]>
jpreese
force-pushed
the
update-pr-workflow
branch
from
12ace0c to
3efdd35
Compare
|
@jpreese v1 release of |
Thanks! Will update soon |
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.
Updating the actions in the PR workflow to resolve the
nodedeprecation warnings. There is still one that remains from theregallinter, but we'll have to wait for @anderseknert to cut a new release.Had to update our
batsaction tobats-core/[email protected]because the one we're using no longer appears to be maintained. Regardless, should be for the best coming from thecoreteam.Some linting errors seemed to have popped up as well from this (or just bad timing with a release from the
golangci-lintteam) so those have been addressed as well.