workflows: Replace deprecated :set-output #6024
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
|
Haha, I involuntarily tested the positive case here, as we currently consider workflow changes to affect the deployment. That is nonsense, I'll fix that in a separate commit. |
These don't affect the deployment.
This causes a "will soon be removed" warning, see https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
martinpitt
force-pushed
the
drop-set-output
branch
from
284c071 to
d51ce15
Compare
|
With the second commit, it doesn't run cockpituous, so we have coverage for both cases. |
jelly
approved these changes
Mar 6, 2024
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.
This causes a "will soon be removed" warning, see
https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
This is also included in cockpit-project/cockpituous#587 where it covers the "positive" case of a changed repo with a container rebuild. Here it should not run cockpituous test.