chore(repo): use new output nomenclature for dev builds #338
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
this commit updates all workflows using the "old" output nomenclature to use the newer variant. `set-output` was deprecated on 2023.10.11, in favor of a new syntax - https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/ starting 2023.05.31, `set-output` is intended to be disabled. applying this commit will allow the dev build workflow
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.
What is the current behavior?
Our tech debt burndown job uses the
set-outputsyntax.set-outputwas deprecated on 2022.10.11, infavor of a new syntax - https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/. starting 2023.05.31,
set-outputis intended to be disabled.GitHub Issue Number: N/A
What is the new behavior?
this commit updates all workflows using the "old" output nomenclature to
use the newer variant. applying this commit will allow the tech debt burndown to continue to function as
expected.
Does this introduce a breaking change?
Testing
Other information
Waiting for us to discuss the dev build issues (see slack for this repo) before marking this ready to review