You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use expo/expo-github-action@v7 and/or expo/expo-github-action/preview-comment@v7 in a GitHub workflow.
Expected behavior
There should be no deprecation warning appearing when using Expo actions.
Actual behavior
What did it actually result in?
We see deprecation warnings appearing when using Expo actions:
Additional context
It seems Expo GitHub Actions doesn't directly use set-output command but uses setOutput from @action/core library, which uses the deprecated set-output command. Luckily, the issue was fixed (without API breakage) in version 1.10.0. Upgrading to that version should solve the issue. If the action is rebuilt, the package.json is correctly set up to pick the latest minor version. However, it would be safe to upgrade to 1.10.0 to make sure.
The text was updated successfully, but these errors were encountered:
Description of the bug
GitHub announced that
set-output
command is now deprecated. This deprecation spam any CI build using Expo GitHub Actions with a deprecation message.To Reproduce
Use
expo/expo-github-action@v7
and/orexpo/expo-github-action/preview-comment@v7
in a GitHub workflow.Expected behavior
There should be no deprecation warning appearing when using Expo actions.
Actual behavior
What did it actually result in?
We see deprecation warnings appearing when using Expo actions:
Additional context
It seems Expo GitHub Actions doesn't directly use
set-output
command but usessetOutput
from@action/core
library, which uses the deprecatedset-output
command. Luckily, the issue was fixed (without API breakage) in version 1.10.0. Upgrading to that version should solve the issue. If the action is rebuilt, thepackage.json
is correctly set up to pick the latest minor version. However, it would be safe to upgrade to 1.10.0 to make sure.The text was updated successfully, but these errors were encountered: