![]() ![]() ![]() This means that we expect PowerShell 7 to be generally available (GA) about a month after. ![]() As mentioned in the PowerShell 7 announcement blog, we will be changing the support life-cycle to align with. If you are using self-hosted runners make sure they are updated to version 2.297.0 or greater.Īction authors who are using the toolkit should update the package to v1.10.0 or greater to get the updated saveState and setOutput functions.Īction and workflow authors who are using save-state or set-output via stdout should update to use the new environment files. For more details on what’s new, check out our changelog on GitHub. Starting 1st June 2023 workflows using save-state or set-output commands via stdout will fail with an error. We are monitoring telemetry for the usage of these commands and plan to fully disable them on 31st May 2023. Starting today runner version 2.298.2 will begin to warn you if you use the save-state or set-output commands via stdout. To avoid untrusted logged data to use save-stateand set-output workflow commands without the intention of the workflow author we have introduced a new set of environment files to manage state and output. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |