Upgrade @actions/core to fix set-output deprecation warning #182
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 PR resolves the deprecation warning about the
set-outputcommand by upgrading@actions/corefrom v1.10.0 to v1.11.1.Problem
The action was generating deprecation warnings:
Root Cause
The project was using
@actions/corev1.10.0, which still used the deprecatedset-outputcommand internally when callingsetOutput().Solution
Upgraded to
@actions/corev1.11.1, which automatically uses the new environment file approach when theGITHUB_OUTPUTenvironment variable is available (which it is in modern GitHub Actions runners).How it works
The updated
setOutputfunction now:GITHUB_OUTPUTenvironment variable is setset-outputcommand for backward compatibilityTesting
Verified that
setOutputcalls now write to theGITHUB_OUTPUTenvironment file using the proper format:Changes
@actions/corefrom^1.10.0to^1.11.1in package.jsonFixes #155.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.