github-actions

5541,521

Discussions related to GitHub Actions

rssabout 2 hours ago(edited)

Workflow dispatch API now returns run IDs
When you trigger a workflow using the GitHub Actions workflow dispatch API endpoint, you’ll now have the option to receive metadata in the response that helps you map your request…
The post Workflow dispatch API now returns run IDs appeared first on The GitHub Blog.

rss6 days ago(edited)

Updated GitHub status page experience
We’ve updated the GitHub status page to make incident information easier to find and more useful during an active event. The status site now includes a 90-day historical view of availability and…
The post Updated GitHub status page experience appeared first on The GitHub Blog.

rss6 days ago(edited)

GitHub Agentic Workflows are now in technical preview
GitHub Agentic Workflows let you automate repository tasks using AI agents that run within GitHub Actions. Write workflows in plain Markdown instead of complex YAML, and let AI handle intelligent…
The post GitHub Agentic Workflows are now in technical preview appeared first on The GitHub Blog.

rss14 days ago(edited)

GitHub Actions: Self-hosted runner minimum version enforcement extended
We’ve extended the timeline for configuration‑time version enforcement of the minimum self‑hosted runner requirement by one week. You now have until March 16, 2026 to upgrade your runners to v2.329.0 or later.…
The post GitHub Actions: Self-hosted runner minimum version enforcement extended appeared first on The GitHub Blog.

rss14 days ago(edited)

GitHub Actions: Early February 2026 updates
This month, GitHub Actions introduces new capabilities, including custom runner autoscaling, expanded security controls for all users, and early access to new Windows and macOS runner images. GitHub Actions runner…
The post GitHub Actions: Early February 2026 updates appeared first on The GitHub Blog.

MB15 days ago

So following the recent GHA security incident ... we only allow GHA that are pinned to SHA's.

How hard and how much of a problem would it be to make sure all your (composite?) actions in org are pinned to SHA's?

https://dev.to/suzukishunsuke/pin-github-actions-to-a-full-length-commit-sha-for-security-2n7p

rss20 days ago(edited)

Docker and Docker Compose version upgrades on hosted runners
On February 9th, 2026, Docker and Docker Compose will be updated on all Windows and Ubuntu runner images except ubuntu-slim. This update allows you to take advantage of the latest…
The post Docker and Docker Compose version upgrades on hosted runners appeared first on The GitHub Blog.

rss21 days ago(edited)

GitHub Actions: Smarter editing, clearer debugging, and a new case function
We’ve shipped several improvements to GitHub Actions that make it easier to write, validate, and troubleshoot workflow logic, especially when you rely on if: conditionals to control what runs. Here…
The post GitHub Actions: Smarter editing, clearer debugging, and a new case function appeared first on The GitHub Blog.

rss21 days ago(edited)

arm64 standard runners are now available in private repositories
Linux and Windows arm64 standard GitHub-hosted runners are now supported in private repositories. You can now use these free-tier eligible arm64 runners in all repositories, letting you take advantage of…
The post arm64 standard runners are now available in private repositories appeared first on The GitHub Blog.

rss28 days ago(edited)

1 vCPU Linux runner now generally available in GitHub Actions
GitHub Actions 1 vCPU Linux runners are now generally available. All customers can now take advantage of these lower cost runners. These runners are optimized for automation tasks, issue operations,…
The post 1 vCPU Linux runner now generally available in GitHub Actions appeared first on The GitHub Blog.

rssabout 1 month ago(edited)

Strengthen your supply chain with code-to-cloud traceability and SLSA Build Level 3 security
You can now link build artifacts like containers and binaries to GitHub and add storage and deployment context, even if the artifacts live outside GitHub. This helps you get code-to-cloud…
The post Strengthen your supply chain with code-to-cloud traceability and SLSA Build Level 3 security appeared first on <a href="https://github.blog/">The...

rssabout 1 month ago(edited)

Rate limiting for actions cache entries
GitHub Actions cache now has a rate limit of 200 uploads/minute per repo. This limit only impacts uploads of new cache entries—it does not impact cache entries that are downloaded…
The post Rate limiting for actions cache entries appeared first on The GitHub Blog.

rssabout 1 month ago(edited)

New fine-grained permission for artifact metadata is now generally available
GitHub has introduced a new artifact_metadata permission to give you more precise control over API access to artifact-related metadata. This permission replaces the broader contents:read and contents:write permissions for the…
The post New fine-grained permission for artifact metadata is now generally available appeared first on <a href="https://github.blog/">The...

RBabout 2 months ago

prek, marketed as better than pre-commit and written in rust. i saw it was used on salesforce/policy_sentry. has anyone had experience with this? is it better than pre-commit ?

https://prek.j178.dev/
https://github.com/j178/prek

rssabout 2 months ago(edited)

Reduced pricing for GitHub-hosted runners usage
Reduced costs for GitHub-hosted runners are now in effect. We announced this update on December 16, 2025. GitHub users will see price reductions of up to 39% for GitHub-hosted runners,…
The post Reduced pricing for GitHub-hosted runners usage appeared first on The GitHub Blog.

rssabout 2 months ago(edited)

Improved performance for GitHub Actions workflows page
GitHub Actions workflow pages now successfully render workflows with more than 300 jobs. We’ve implemented lazy loading to smoothly handle large workflows. In addition, you can now filter jobs based…
The post Improved performance for GitHub Actions workflows page appeared first on The GitHub Blog.

PePe Amengualabout 2 months ago

shameless plug incoming; In my weekend adventures and or late week days I created :
https://github.com/jamengual/enterprise-approval-engine
I have released it to Github Marketplace give it a test, give feedback, ⭐️ the repo if you like it and or request features.
you can see it in action here:
https://github.com/jamengual/enterprise-approval-engine/issues/7

Cyril (runs-on.com)2 months ago

They are suspending the change
https://github.com/orgs/community/discussions/182186

erik2 months ago

• On March 1, 2026, we are introducing a new $0.002 per-minute GitHub Actions cloud platform charge that will apply to self-hosted runner usage. Any usage subject to this charge will count toward the minutes included in your plan.

rss2 months ago(edited)

Coming soon: Simpler pricing and a better experience for GitHub Actions
On January 1, 2026, GitHub will reduce the price of GitHub-hosted runners by up to 39% depending on the machine type used. The free usage minute quotas will remain the…
The post Coming soon: Simpler pricing and a better experience for GitHub Actions appeared first on The GitHub Blog.

rss2 months ago(edited)

Better diagnostics for VNET injected runners and required self-hosted runner upgrades
GitHub-hosted larger runners with Azure private networking (Azure VNET-injection) now display detailed network diagnostics when connectivity issues occur. Instead of generic pool errors, you’ll see: Per-endpoint visibility: Drill down into…
The post Better diagnostics for VNET injected runners and required self-hosted runner upgrades appeared first on <a...

rss3 months ago(edited)

Actions workflow dispatch workflows now support 25 inputs
You can now use up to 25 inputs on workflows triggered via the workflow_dispatch trigger. The previous limit was 10 which was challenging for the community. This new limit gives…
The post Actions workflow dispatch workflows now support 25 inputs appeared first on The GitHub Blog.

erik3 months ago

@Igor Rodionov

Marat Bakeev3 months ago

In a github action for atmos-terraform-plan we have this section:

  atmos-plan:
    needs: ["atmos-affected"]
    if: ${{ needs.atmos-affected.outputs.has-affected-stacks == 'true' }}
    name: Plan (${{ matrix.name }})
    uses: ./.github/workflows/atmos-terraform-plan-matrix.yaml
    strategy:
      matrix: ${{ fromJson(needs.atmos-affected.outputs.stacks) }}
      max-parallel: 1 # This is important to avoid ddos GHA API
      fail-fast: false # Don't fail fast to avoid locking TF State
    with:
      stacks: ${{ matrix.items }}
      atmos-version: ${{ vars.ATMOS_VERSION }}
      atmos-config-path: ${{ vars.ATMOS_CONFIG_PATH }}
      sha: ${{ github.event.pull_request.head.sha }}
    secrets: inherit

Is the limit of 1 really that strict?

 max-parallel: 1 # This is important to avoid ddos GHA API

and in atmos-terraform-plan-matrix.yaml we have max-parallel: 10... so is it 1 or 10?

rss3 months ago(edited)

Code scanning default setup bypasses GitHub Actions policy blocks
GitHub code scanning default setup now runs even if your organization has GitHub Actions policies that restrict which workflows can run. In the past, restrictive actions policies could block code…
The post Code scanning default setup bypasses GitHub Actions policy blocks appeared first on The GitHub Blog.

rss3 months ago(edited)

GitHub Actions cache size can now exceed 10 GB per repository
GitHub Actions cache size can now exceed 10 GB per repository You can now store more build dependencies between workflow runs with expanded GitHub Actions cache storage. Repositories can go…
The post GitHub Actions cache size can now exceed 10 GB per repository appeared first on The GitHub Blog.

rss3 months ago(edited)

New GitHub Actions OIDC token claims
GitHub Actions OpenID Connect (OIDC) token claims now include check_run_id This enhancement enables fine-grained, attribute-based access control and improves auditability for workflows that integrate with external services. Platform teams often…
The post New GitHub Actions OIDC token claims appeared first on The GitHub Blog.

Carter Danko3 months ago

I think there is a bug (or at least some documentation that I may be missing and it's just PEBKAC) around the cloudposse/github-action-docker-build-push action. I've created the bug tracking it here https://github.com/cloudposse/github-action-docker-build-push/issues/86

rss3 months ago(edited)

Actions pull_request_target and environment branch protections changes
GitHub is updating how GitHub Actions’ pull_request_target and environment branch protection rules are evaluated for pull-request-related events. These changes will take effect on 12/8/2025. They aim to reduce security critical…
The post Actions pull_request_target and environment branch protections changes appeared first on <a href="https://github.blog/">The GitHub...

rss4 months ago(edited)

New releases for GitHub Actions – November 2025
Increased limits for reusable workflows You can now use up to 10 nested reusable workflows and call up to 50 workflows in total from a given workflow run. The previous…
The post New releases for GitHub Actions – November 2025 appeared first on The GitHub Blog.

rss4 months ago(edited)

Upcoming deprecation of CodeQL Action v3
On October 7, 2025, we released CodeQL Action v4, which runs on the Node.js 24 runtime. CodeQL Action v3 will be deprecated at the same time as GHES 3.19, which…
The post Upcoming deprecation of CodeQL Action v3 appeared first on The GitHub Blog.

toka4 months ago

Hey, I'm using https://github.com/cloudposse/github-action-atmos-affected-stacks and I got stuck.
I have created a PR which introduces 3 stacks and number of components, and was able to produce GH Job matrix just fine. Then PR got merged into main branch, and I expect to execute Atmos Terraform Apply from the main branch after merging.

The thing is, PR was left open for couple of days and the Matrix artifact expired.
I cannot get to re-run it in a way that would produce the same matrix without changing inputs or settings in the components themselves - I cannot afford that since my goal is to make Terraform Import during Atmos Terraform Apply without any changes in infra.
Triggering again against master brach results in no changed being detected.
Any ideas how to get around that?

rss4 months ago(edited)

Copilot coding agent now supports self-hosted runners
You can now configure Copilot coding agents’s development environment to run in your own infrastructure using self-hosted GitHub Actions runners managed by Actions Runner Controller (ARC). With this setup, you…
The post Copilot coding agent now supports self-hosted runners appeared first on The GitHub Blog.

rss4 months ago(edited)

Custom images for GitHub-hosted runners are now available in public preview
Custom images for GitHub-hosted runners are now available in public preview. This feature allows you to start with a GitHub-curated base image and build your own virtual machine image tailored…
The post Custom images for GitHub-hosted runners are now available in public preview appeared first on The GitHub Blog.

rss4 months ago(edited)

1 vCPU Linux runner now available in GitHub Actions in public preview
GitHub Actions 1 vCPU Linux runners are now in public preview. Customers looking to run lightweight operations can take advantage of these lower cost runners. These runners are optimized for…
The post 1 vCPU Linux runner now available in GitHub Actions in public preview appeared first on The GitHub Blog.

Alek4 months ago(edited)

Hello Team! Still new to Atmos, so please excuse me if the question is basic.

Having made a bunch of changes to our EKS addon placement, I'm hitting some issues executing apply using the official Atmos GitHub Actions: plan files have differences

My workflow was straight forward - I made a PR with changes to EKS addon versions and configuration, which generated a matrix of successful plans across all my regions in prod. Then, I merged the PR, with auto-apply label on it. Still, the apply to my stacks fail - but it does not fail reliably. Some matrix jobs pass, and changes are applied, but others fail with this error.

Something I considered was to delete the old planfiles from the S3 bucket manually and retry, but I wanted to check here if there's something I am missing.

Component:

<http://github.com/cloudposse-terraform-components/aws-eks-cluster.git//src?ref=v1.535.0|github.com/cloudposse-terraform-components/aws-eks-cluster.git//src?ref=v1.535.0>

rss4 months ago(edited)

Actions Runner Controller release 0.13.0
Actions Runner Controller (ARC) release 0.13.0 is now available and provides improvements in storage, networking, platform, and metrics. Enable container hooks to remove storage limitations ARC now supports container lifecycle…
The post Actions Runner Controller release 0.13.0 appeared first on The GitHub Blog.

Sean Turner4 months ago(edited)

Hey all, any idea what's the best way to enable a Github Application to approve PRs?

Usecase:
Python library versions are published in upstream repo
Downstream repos trigger a GHA that add the new version and open a PR that needs to be approved (gets put in merge queue automatically)

So I want to automate the approval of the PR (which is perfect as we're happy as long as automated tests are passing)

I've learned through doing that a GHA (authenticating to Github with the GHA Token) in one run cannot approve a PR created by another GHA with the same auth paradigm
I've also learned that while a Github Application can approve a PR (I impersonated the App for testing purposes), branch protection rules mark this approval as an "un-approved reviewer"

In the repo I tested (downstream consumer of the libray) we don't actually have a .github/CODEOWNERS defined. So I suppose by default this is determined by the Collaborators and teams repository-level settings.
I guess looking at your repos I see a number of commits are by https://github.com/actions-user?

Jay Patel5 months ago

Hey Folks
is there any open-source or self-hosted tool that can monitor my GitHub-Actions Pieplines??

rss5 months ago(edited)

New date for enforcement of cache eviction policy
We’re delaying the enforcement of a new cache eviction policy for GitHub Actions from mid-October to November. Currently, each repository has a maximum cache size of 10 GB, and we…
The post New date for enforcement of cache eviction policy appeared first on The GitHub Blog.

rss5 months ago(edited)

Deprecation of Node 20 on GitHub Actions runners
Node20 will reach end-of-life (EOL) in April of 2026. As a result we have started the deprecation process of Node20 for GitHub Actions. We plan to migrate all actions to…
The post Deprecation of Node 20 on GitHub Actions runners appeared first on The GitHub Blog.

rss5 months ago(edited)

GitHub Actions: macOS 13 runner image is closing down
The macOS 13 runner image will be retired by December 4th, 2025. To raise awareness of the upcoming removal, jobs using macOS 13 will temporarily fail during the scheduled brownout…
The post GitHub Actions: macOS 13 runner image is closing down appeared first on The GitHub Blog.

rss5 months ago(edited)

Actions: YAML anchors and non-public workflow templates
Reuse workflow configuration with YAML anchors GitHub Actions now supports YAML anchors, a top request from the GitHub community. With YAML anchors, you can reuse configuration across your workflows and…
The post Actions: YAML anchors and non-public workflow templates appeared first on The GitHub Blog.

rss5 months ago(edited)

Actions: macOS 26 image now in public preview
Developers looking to use the latest Xcode technology and build and test their iOS applications can use the new macOS 26 image natively in their GitHub Actions workflow runs. The…
The post Actions: macOS 26 image now in public preview appeared first on The GitHub Blog.

Erik Osterman (Cloud Posse)5 months ago(edited)

https://github.com/runs-on/runs-on/issues/359#issuecomment-3266737345

If you're using runs-on and experiencing trouble today, this comment will help you.

rss6 months ago(edited)

GitHub Actions policy now supports blocking and SHA pinning actions
GitHub Actions is powered by a diverse ecosystem of first-party and community contributed actions. If one of these actions has a vulnerability or is compromised by a malicious actor, it…
The post GitHub Actions policy now supports blocking and SHA pinning actions appeared first on The GitHub Blog.

rss7 months ago(edited)

arm64 hosted runners for public repositories are now generally available
Starting today, Linux and Windows arm64 standard hosted runners in public repositories are generally available. Developers can take advantage of the performance benefits of using arm64 processors or run their…
The post arm64 hosted runners for public repositories are now generally available appeared first on The GitHub Blog.

Matt B7 months ago

https://youtu.be/GmHjSbYriJ0

rss7 months ago(edited)

GitHub Actions: New APIs and windows-latest migration notice
New REST APIs for Actions settings Today, GitHub Actions is launching new REST APIs for managing actions settings. The following settings are now accessible via these new endpoints: Approval for…
The post GitHub Actions: New APIs and windows-latest migration notice appeared first on The GitHub Blog.

rss7 months ago(edited)

GitHub Actions now offers M2 Pro-powered hosted runners in public preview
The GitHub macOS hosted runner fleet is being upgraded to M2 Pro-powered machines on our largest runners. Starting today the macOS XLarge runner sku now utilizes a 5 vCPU M2…
The post GitHub Actions now offers M2 Pro-powered hosted runners in public preview appeared first on The GitHub Blog.

#github-actions

github-actions