Search results for: GitHub Actions

Customers can now deterministically restrict their workflows to run on a specific set of runners using the names of their runner groups in the runs-on key of their workflow YAML.…

GitHub Actions workflows often specify the version of an action using the commit SHA. Since commit SHAs are immutable, this ensures that Actions always picks the same version. Commit SHAs,…

GitHub Actions changed how developers automate workflows with GitHub. Today, we’re introducing a new navigation to manage your GitHub Actions experience, improving discoverability and accessibility as well as opening up future feature opportunities.

Starting today, customers can now enjoy larger runners without any pre-configuration work. GitHub now automatically creates a default runner group configured with four larger runners of our most popular sizes…

OpenID Connect (OIDC) support in GitHub Actions enables secure cloud deployments using short-lived tokens that are automatically rotated for each deployment. You can now use the enhanced OIDC support to…

We’ve made exciting design improvements to GitHub Actions to promote better discoverability and accessibility. The improvements include: An improved navigation experience that makes it easier to search workflows and workflow…

GitHub now supports using the -latest image label on your larger hosted runners. With the -latest label developers can be sure that their workflows use the latest available GA image…

24-July-2023 Update: Our telemetry shows significant usage of these commands so we have decided to postpone the removal. To learn more, visit the latest changelog post. To avoid untrusted logged…

macOS 12 became generally available on GitHub-hosted runners in June 2022. Over the next 10 weeks, jobs using the macos-latest runner label will migrate from macOS 11 to 12. During…

Actions runner support for Windows ARM hardware, is now in public beta . This provides teams with the capability to run self-hosted Windows workflows in a Windows ARM64 runtime. There…

Additional information has been added to the payload of github.event for scheduled runs. Before this change, github.event for scheduled runs would only include the cron schedule. This change adds information…

GitHub Actions customers can now dynamically name their workflow runs. The new run-name feature will accept expressions and be displayed on the list of workflow runs. For more information on…

Node 12 has been out of support since April 2022, as a result we have started the deprecation process of Node 12 for GitHub Actions. We plan to migrate all…

The GitHub Actions team has done lots of work to improve the performance and resource consumption of Actions on GHES in the past year.

Customers will now be able to use the GITHUB_TOKEN with workflow_dispatch and repository_dispatch events to trigger workflows. Prior to this change, events triggered by GITHUB_TOKEN would not create a new…

Today, we are announcing the public beta of larger GitHub hosted runners for GitHub Actions for Team and Enterprise plans 🎉 🎉 The new larger runners provide new capabilities for…

Now your team can spend less time managing infrastructure and more time writing code.

OpenID Connect (OIDC) support in GitHub Actions is now enhanced to support secure cloud deployments at scale. Org & repo admins can use the new OIDC API support to: enable…

Reusable workflows can now be called from a matrix and other reusable workflows. You can now nest up to 4 levels of reusable workflows giving you greater flexibility and better…

This feature is available to repositories enrolled in the Pull Request Merge Queue beta. A new webhook event and GitHub Actions workflow trigger (merge_group) makes it easier to run required…

GitHub Pages now builds with GitHub Actions by default across all repositories. For more details, see this blog post.