
GitHub Actions: New runner release v2.262.1
We have released a new version of the GitHub Actions runner. Features Sample scripts to automate scalable runners (#427) Raise warning when action input does not match action.yml (#429) Add…
We have released a new version of the GitHub Actions runner. Features Sample scripts to automate scalable runners (#427) Raise warning when action input does not match action.yml (#429) Add…
You can now see which version of our hosted virtual environments your job was executed on. In the Set up job portion of your logs you will now find: Operating…
We have released a v2 version of the setup-python action. New features: Ability to download, set up, and install Python packages from actions/python-versions that do not come preinstalled on GitHub-hosted…
We have released v2 versions of the upload-artifact and download-artifact actions. The actions have been completely rewritten using typescript in contrast to the v1 versions which are plugins tied to…
GitHub Actions now supports self-hosted runners at the organization level, where they can be used to process jobs for multiple repositories in an organization. The Actions API has been updated…
GitHub Actions continues its community momentum and ships new features for enterprises and developers.
Anybody with write access to the repo will be able to delete the logs just clicking a button in the workflow run page. The metadata about the workflow run will…
Starting May 20th, we will remove self-hosted runners from service that haven’t connected to service for 30 days. You will need to reconfigure your self-hosted runner after it gets removed…
We have released a new version of the GitHub Actions runner. Features Better telemetry and tracing for self-hosted runners (#405) Workaround some SIP limitations in macOS (#416) Support for custom…
The GitHub Actions runner now sets the CI=true environment variable by default. Learn more about GitHub Actions default environment variables
We’ve added some new workflow features to GitHub Actions based on your feedback. Workflow and job level run defaults. You can specify the shell and working-directory for the run action…
We want to thank everyone who participated in the GitHub Actions Hackathon. We had hundreds of submissions, so here’s our top picks.
The GitHub Actions API is now generally available and out of beta. Thank you to everyone who tried out this API and provided feedback during the beta period. For support,…
Starting March 5, we’re hosting an online GitHub Actions Hackathon challenging you to create original Actions.
Starting April 6, 2020, Python 2 will no longer be offered on any hosted virtual environments. Python 2 was sunset on January 1, 2020 and is not being improved or…
Starting March 3rd, 2020, the Ubuntu virtual environments will no longer start the MySQL service automatically. If you are using MySQL, this may be a breaking change for your workflows.…
In this deep dive, we cover how our daily schema migrations amounted to a significant toil on the database infrastructure team, and how we searched for a solution to automate the manual parts of the process.
Self-Hosted Runners now fully support environments that use a proxy server to connect to GitHub. You can add your proxy server as a Runner setting and leverage common Unix-style proxy…
Manage secrets, make use of self-hosted runners, and more with the GitHub Actions API—now available in beta.
The GitHub Actions API beta is now available. In addition to reading workflow and run data, Actions users can now automate common scenarios like managing secrets or registering runners. Learn…
We have changed the artifact download experience in GitHub Actions so it no longer adds an extra root directory to the downloaded archive. Previously, if you uploaded the following files…
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.