You can now enable debug logging when you re-run jobs in a GitHub Actions workflow run. This gives you additional information about the job's execution and its environment which can help you diagnose failures.
To enable debug logging, select "Enable debug logging" in the re-run dialog.
You can also enable debug logging using the API or the command-line client.
For more details see
Re-running workflows and jobs.
For questions, visit the GitHub Actions community.
To see what's next for Actions, visit our public roadmap.
You can now sign up for Sponsors if you have a bank account and tax residence in India. Read about the rollout on our blog and stay tuned for more news on expansion.
As always, you can sponsor projects from wherever GitHub does business and join the Sponsors waitlist if we're not yet in your region.
Actions authors can now specify that their action can run in Node.js 16 by specifying runs.using as node16 in the action's action.yml. This is in addition to the existing Node.js 12 support; actions can continue to specify runs.using: node12 to use the Node.js 12 runtime.
Runners supporting Node.js 16 actions are available on all GitHub-hosted runners and in GitHub Enterprise Server 3.4 and newer. GitHub Enterprise Server 3.3 and newer can manually install a newer runner to add support for Node.js 16 based actions.
As a result, actions authors who move from targeting Node.js 12 to Node.js 16 should release with a new major version number to communicate that there is a possible breaking change for GitHub Enterprise Server 3.3 and earlier.