Ubuntu-latest upcoming breaking changes
We will migrate the ubuntu-latest
label to ubuntu 24
starting on December 5, 2024 and ending on January 17, 2025. The ubuntu 24
image has a different set of tools and packages than ubuntu 22
. We have made cuts to the list of packages so that we can maintain our SLA for free disk space. This may break your workflows if you depend on certain packages that have been removed. Please review this list to see if you are using any affected packages.
Artifacts v3 brownouts
Artifact actions v3 will be closing down by January 30, 2025. To raise awareness of the upcoming removal, we will temporarily fail jobs using v3 of actions/upload-artifact
or actions/download-artifact
. Builds that are scheduled to run during the brownout periods will fail. The brownouts are scheduled for the following dates and times:
- January 9, 12pm – 1pm EST
- January 16, 10am – 2pm EST
- January 23, 9am – 5pm EST
Changes to workflow validation for pull requests originating from forked repositories
Currently, you can prevent Actions workflows from automatically running on pull requests made from forked repositories. Actions evaluates whether the actor initiating the request is trusted based on the repository’s settings. Effective today, Actions will require validation of both the pull request author and the event actor to determine if a workflow should run from a pull request event originating from a forked repository. For more information on for pull request approvals, see our documentation.
New webhook rate limit
As GitHub continues to invest in availability, GitHub Actions is introducing a new webhook rate limit per repository. Each repository is now limited to 1500 triggered events every 10 seconds. For more details about the new webhook rate limit, please refer to our documentation.
Updates to the network allow list for self-hosted runners and Azure private networking
With the upcoming GA of Immutable Actions, Actions will now be stored as packages in the GitHub Container Registry. Please ensure that your self-hosted runner allow lists are updated to accommodate the network traffic. Specifically, you should allow traffic to ghcr.io
and *.actions.githubusercontent.com
. If you require more specific domains, you can use pkg.actions.githubusercontent.com
instead of *.actions.githubusercontent.com
.
This update also affects runners in all versions of GitHub Enterprise Server that use the GitHub Connect feature to download actions directly from github.com. Customers are advised to update their self-hosted runner network allow lists accordingly. For further guidance on communication between self-hosted runners and GitHub, please refer to our documentation.
Additionally, our guidance for configuring Azure private networking has been updated to account for the the new domains. The following IP addresses have been added to the NSG template in our documentation.
– 140.82.121.33/32
– 140.82.121.34/32
– 140.82.113.33/32
– 140.82.113.34/32
– 140.82.112.33/32
– 140.82.112.34/32
– 140.82.114.33/32
– 140.82.114.34/32
– 192.30.255.164/31
– 4.237.22.32/32
– 20.217.135.1/32
– 4.225.11.196/32
– 20.26.156.211/32