
GitHub Actions—scheduled jobs maximum frequency is changing
In order to provide a more reliable experience, we’ve set the minimum time period for scheduled runs to 5 minutes. A schedule of * * * * * which would…
In order to provide a more reliable experience, we’ve set the minimum time period for scheduled runs to 5 minutes. A schedule of * * * * * which would…
On November 4th, the macOS virtual environment for GitHub Actions will update to Catalina (v10.15), the latest version of macOS X. After the update, jobs using the macos-10.14 virtual environment will…
The Windows Server 2016 virtual environment will be removed from GitHub Actions in January 2020. You will need to update your workflow files to run on windows-latest which will run…
The number of jobs you can run concurrently now depends on your GitHub plan and is shared across all repositories in your account. See Usage Limits for more information.
We’ve fully deployed several updates to the GitHub Actions virtual environments. Highlights include: Windows Server 2016 R2 Added Android SDK Build Tools 29.0.0 and 29.0.2 Added Android SDK Platform 10…
GitHub Actions is changing how we evaluate some events in order to make sure we always run workflows from known refs in your repository. Going forward the following events will…
We’ve fully deployed updates to the GitHub Actions macOS 10.14 virtual environment. Highlights include: Upgraded macOS 10.14.6 (18G95) to 10.14.6 (18G103) Upgraded NVM 12.11.0 to 12.11.1 Upgraded Go 1.13 to…
We will remove Python 3.4 and Ruby 2.3 from all virtual environments in a future update since both reached end-of-life in March 2019.
On 10/23/2019 we will change the default shell for the run step on Windows runners to PowerShell. If your run step contains Windows batch scripting you should update it to…
GitHub Actions are triggered by webhook events. The original payload of the event is stored in a file that actions can read at workflow/event.json (see the docs). We’ve made a…
Check out a few of our favorite GitHub Actions created by our partners at Mabl, Codefresh, GorillaStack, and GitKraken.
To publish an action to the GitHub Marketplace, you are now required to have a properly formed actions metadata file placed at action.yml in the root of your action’s repository.…
We’re sharing examples of productive workflows within the open source community.
We’ve fully deployed updates to the GitHub Actions macOS 10.14 virtual environment: Added Java 13 Upgraded NVM 12.10.0 to 12.11.0 Upgraded CocoaPods 1.7.5 to 1.8.0 Upgraded Azure CLI 2.0.72 to…
GitHub Actions has new settings for organizations and repository owners to limit the usage of external Actions.
Users and organizations who register for the GitHub Actions and GitHub Package Registry betas are now automatically granted access.
It’s now even easier to create and edit a GitHub Actions workflow with the updated editor. We’ve provided inline auto-complete and lint as you type so you can say goodbye…
Edit your GitHub Actions workflow files easier with features to help you minimize errors and more.
We have stopped running HCL workflows, as announced on the 17th. If you still have HCL workflows, please convert your .github/main.workflow files using the migrate tool.
The GitHub Actions workflow syntax has new features based on feedback from our community. Env at the workflow and job level It is common to need define a set of…
GitHub Actions is built on top of webhooks and checks and uses the CheckSuiteEvent for re-running workflows. Using the CheckSuiteEvent for re-run can lead to non-deterministic results due to the…
Build what’s next on GitHub, the place for anyone from anywhere to build anything.
Last chance: Save $700 on your IRL pass to Universe and join us on Oct. 28-29 in San Francisco.