# GitHub Actions

GitHub's platform for automating software development workflows, including CI/CD, in repositories.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Automatic RSpec Sharding on GitHub Actions

DevFeed: [Automatic RSpec Sharding on GitHub Actions](<https://devfeed.tech/articles/automatic-rspec-sharding-on-github-actions-144065.md>)

Original publisher: [Read original article](<https://code.dblock.org/2026/11/19/automatic-rspec-sharding-on-github-actions.html>)

Author: Daniel Doubrovkine (dblock@dblock.org)

Published: 2026-11-19T00:00:00Z

Content type: tutorial

Language: en

Sources: [Daniel Doubrovkine](<https://devfeed.tech/sources/daniel-doubrovkine.md>)

Topics: [dynamic test splitting](<https://devfeed.tech/topics/dynamic-test-splitting.md>), [RSpec](<https://devfeed.tech/topics/rspec.md>), [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [sharding](<https://devfeed.tech/topics/sharding.md>)

Tags: [ci](<https://devfeed.tech/tags/ci.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [rails](<https://devfeed.tech/tags/rails.md>), [rspec](<https://devfeed.tech/tags/rspec.md>), [ruby](<https://devfeed.tech/tags/ruby.md>), [sharding](<https://devfeed.tech/tags/sharding.md>), [testing](<https://devfeed.tech/tags/testing.md>), [timing](<https://devfeed.tech/tags/timing.md>)

### AI overview

The `parallel_tests-ci` reusable GitHub Actions workflow cut Posebook's RSpec time from 395 seconds serially to under 80 seconds on eight workers in every run shown, excluding setup and spec loading. It requires Ruby 3.3 or newer and can run database or other setup commands on each worker. Without timing history, `parallel_tests` groups spec files by size; after successful default-branch pushes, the workflow stores per-file timings in a `runtime.log` artifact. Later runs use the newest available artifact from recent successful runs of the same workflow on the default branch to balance worker loads. Pull requests can use that history but cannot update it.

### Source excerpt

Running RSpec on eight workers got Posebook, a custom Rails CMS, from more than six minutes of RSpec time to about one using parallel_tests-ci that I built to adjust shards automatically as tests get faster or slower, without repeating the GitHub Actions boilerplate for splitting files, running workers, and passing timings between runs. Posebook Benchmarks Each bar shows the slowest worker's RSpec execution time, excluding setup and spec loading. The serial run took 395 seconds. With eight workers, every run shown took less than 80 seconds of RSpec time. Sharding improved further capturing data from previous runs. How to Use It With Ruby 3.3 or newer, add the gem to your Gemfile and run bundle install: gem 'parallel_tests-ci', '0.1.0', require: false In .github/workflows/test.yml, call the reusable workflow at the same version: name: Test on: [push, pull_request] permissions: contents: read actions: read jobs: test: uses: dblock/parallel_tests-ci/.github/workflows/rspec.yml@v0.1.0 with: shards: 8 If your specs need a database or other setup, use the workflow's setup input to run those commands on each worker. How It Works Without timing history, parallel_tests groups spec files by size. After a successful run triggered by a push to the default branch, the workflow saves per-file timings in a runtime.log and uploads it as a GitHub Actions artifact. Before splitting the suite, later runs look for that artifact in recent successful runs of the same workflow on the default branch. They download the newest one still available and use its timings to give each worker roughly the same amount of work. Pull requests can also download the artifact, but cannot update the timing history. Automatic RSpec Sharding on GitHub Actions was originally published by Daniel Doubrovkine at code.dblock.org | tech blog on November 19, 2026.

## Missing Security-Fix Backporting for GitHub Actions Workflows

DevFeed: [Missing Security-Fix Backporting for GitHub Actions Workflows](<https://devfeed.tech/articles/missing-security-fix-backporting-for-github-actions-workflows-139608.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.22519>)

Author: Chengyan Ma, Jieke Shi, Ruidong Han, Weifeng Sun, Yuqing Niu, Yunbo Lyu, Zhou Yang, David Lo

Published: 2026-11-18T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>), [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Static code analysis](<https://devfeed.tech/topics/static-code-analysis.md>), [GitHub](<https://devfeed.tech/topics/github.md>)

Tags: [actions](<https://devfeed.tech/tags/actions.md>), [automated](<https://devfeed.tech/tags/automated.md>), [backporting](<https://devfeed.tech/tags/backporting.md>), [backports](<https://devfeed.tech/tags/backports.md>), [branch](<https://devfeed.tech/tags/branch.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [llm](<https://devfeed.tech/tags/llm.md>), [maintenance](<https://devfeed.tech/tags/maintenance.md>), [matching](<https://devfeed.tech/tags/matching.md>), [patch](<https://devfeed.tech/tags/patch.md>), [release](<https://devfeed.tech/tags/release.md>), [release-branches](<https://devfeed.tech/tags/release-branches.md>), [scan](<https://devfeed.tech/tags/scan.md>), [scanner](<https://devfeed.tech/tags/scanner.md>), [security](<https://devfeed.tech/tags/security.md>), [security-fixes](<https://devfeed.tech/tags/security-fixes.md>), [semantic](<https://devfeed.tech/tags/semantic.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

An audit of GitHub Actions workflow histories found that 224,392 of 474,490 audited release branches remained vulnerable after a fix appeared on the default branch. Of 78,907 already-fixed branches, only 19,476 had plausible backports, at a median lag of 243 days. The study introduces WorkflowBP, which represents fixes as Workflow Semantic Patches and matches jobs and steps by content across divergent branches. A deterministic engine handles resolvable cases; an LLM synthesizes patches for the most divergent cases. On 12,000 unpatched workflow files, it produced scanner-checked backports for 67.9%. Developers confirmed or fixed 44 of 176 issues submitted with generated backports.

### Source excerpt

arXiv:2611.22519v1 Announce Type: new Abstract: GitHub natively supports workflow automation through GitHub Actions, now the dominant CI/CD tool on the platform. Yet keeping these workflows secure remains an ongoing burden: maintainers often patch a vulnerability on the default branch but leave the same flaw on the release and maintenance branches that downstream consumers continue to build from. Carrying a known fix onto these divergent branches, called backporting, is rarely done, and this paper presents the first large-scale empirical study quantifying the resulting gap. From a public corpus of GitHub Actions workflow histories, we mine 1,903,191 workflow-modifying commits, scan each before and after with the static scanner zizmor to identify 69,865 security fixes across 24,238 projects, and audit every release branch to check whether each fix was carried over. The gap is pervasive: 224,392 of 474,490 audited release branches remain vulnerable, and deliberate backporting is rare and slow, with only 19,476 of 78,907 already-fixed branches confirmed as plausible backports at a median lag of 243 days. We thus design WorkflowBP, the first technique for automated security-fix backporting of GitHub Actions workflows. WorkflowBP takes a neuro-symbolic approach: it compiles a default-branch fix into a domain-specific representation called the Workflow Semantic Patch (WSP) and applies it to each divergent branch by matching jobs and steps based on their content rather than their position, while an LLM synthesizes the WSP for the most divergent cases the deterministic engine cannot resolve. On 12,000 real unpatched workflow files from our study, WorkflowBP produces a scanner-checked backport for 67.9%. We further submit 176 issues with WorkflowBP-generated backports to real-world projects, 44 of which have been confirmed or fixed by developers.

## GHA-SmellFix: Taking Action with Agentic LLMs for Detecting and Refactoring GitHub Actions Workflow Smells

DevFeed: [GHA-SmellFix: Taking Action with Agentic LLMs for Detecting and Refactoring GitHub Actions Workflow Smells](<https://devfeed.tech/articles/gha-smellfix-taking-action-with-agentic-llms-for-detecting-and-refactoring-github-actions-workflow-smells-131703.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.14963>)

Author: Anderson Uch\\^oa, Jhefferson Souza, Emanuel \\'Avila, Gabriel Silva, Kevin Lira, Hui Sun, Nelson Ara\\'ujo, Arthur Cordeiro, Rohit Gheyi, Wesley Assun\\c{c}\\~ao

Published: 2026-11-13T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Ground truth / benchmark quality](<https://devfeed.tech/topics/ground-truth-benchmark-quality.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [cs-ma](<https://devfeed.tech/tags/cs-ma.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [llms](<https://devfeed.tech/tags/llms.md>), [refactoring](<https://devfeed.tech/tags/refactoring.md>), [workflow](<https://devfeed.tech/tags/workflow.md>)

### AI overview

GHA-SmellFix evaluates whether splitting GitHub Actions workflow smell detection and refactoring between agents improves results. Across four LLMs and 570 sampled workflow-smell pairs, decomposition did not consistently improve patch quality; its main benefit was gating patch generation, which helped models prone to missed detections and could reduce overhead. Refactoring was generally effective after correct detection, making detection the main end-to-end bottleneck. False positives could still cause unnecessary edits to execution-relevant workflow constructs, so the authors identify reliable abstention and construct-aware validation as practical needs.

### Source excerpt

arXiv:2611.14963v1 Announce Type: new Abstract: Continuous integration and continuous delivery workflows are key artifacts in software projects. In GitHub Actions, they encode build, test, release, deployment, and security automation in YAML. These workflows contain configuration smells affecting security, reliability, maintainability, or operational stability. Existing approaches are mostly rule-based, with rules hard to create and evolve, and typically report findings without fixes. Agentic LLM pipelines can combine contextual detection, transformation selection, and patch generation. Specialized agents can gate refactoring on positive detection verdicts, potentially avoiding unnecessary changes, but it is unclear whether decomposition improves effectiveness or mainly changes overhead. We present GHA-SmellFix, an agentic LLM pipeline for detecting and refactoring GitHub Actions workflow smells. We compare two designs: Joint, where one agent detects and refactors, and Decomposed, where separate agents detect and then refactor. We operationalize 19 smells from an existing catalog with explicit detection criteria, refactoring expectations, exclusion rules, and safety checks, and curate a ground truth of 1,710 (workflow, smell) pairs. We evaluate the designs with four LLMs (GPT-5.4-nano, Gemini 3.5 Flash, Claude Haiku 4.5, and DeepSeek V4 Flash) on 570 sampled pairs. Results show that decomposition does not universally improve patch quality; its main benefit is controlling when patch generation is attempted. It helps models prone to missing smells and can reduce overhead by gating patches. Once a smell is correctly detected, clean refactoring is generally effective, making detection the main end-to-end bottleneck. However, false positives can trigger unnecessary edits to execution-relevant constructs. Practical CI/CD agents thus need reliable abstention and construct-aware validation alongside patch generation.

## GitHub availability report: October 2026

DevFeed: [GitHub availability report: October 2026](<https://devfeed.tech/articles/github-availability-report-october-2026-132661.md>)

Original publisher: [Read original article](<https://github.blog/news-insights/company-news/github-availability-report-october-2026/>)

Author: Jakub Oleksy

Published: 2026-11-13T00:20:16Z

Content type: news

Language: en

Sources: [GitHub Blog](<https://devfeed.tech/sources/github-engineering.md>)

Topics: [Availability](<https://devfeed.tech/topics/availability.md>), [Production Engineering](<https://devfeed.tech/topics/production-engineering.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [GitHub Copilot](<https://devfeed.tech/topics/github-copilot.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [actions](<https://devfeed.tech/tags/actions.md>), [api](<https://devfeed.tech/tags/api.md>), [audit-log](<https://devfeed.tech/tags/audit-log.md>), [audit-logs](<https://devfeed.tech/tags/audit-logs.md>), [availability](<https://devfeed.tech/tags/availability.md>), [azure](<https://devfeed.tech/tags/azure.md>), [blog](<https://devfeed.tech/tags/blog.md>), [cache](<https://devfeed.tech/tags/cache.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [central](<https://devfeed.tech/tags/central.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [company-news](<https://devfeed.tech/tags/company-news.md>), [github](<https://devfeed.tech/tags/github.md>), [github-availability-report](<https://devfeed.tech/tags/github-availability-report.md>), [incidents](<https://devfeed.tech/tags/incidents.md>), [news-insights](<https://devfeed.tech/tags/news-insights.md>), [october](<https://devfeed.tech/tags/october.md>), [october-2026](<https://devfeed.tech/tags/october-2026.md>), [performance](<https://devfeed.tech/tags/performance.md>), [report](<https://devfeed.tech/tags/report.md>), [services](<https://devfeed.tech/tags/services.md>)

### AI overview

GitHub reported eight incidents in October and expanded Azure Central US capacity while addressing reliability risks exposed by the outages. As of November 9, 140 of 151 production services and 32 of 50 MySQL primaries ran there; the region served 63% of migrated-service reads, 66% of monolith reads, and 52% of Git reads. Nine Kubernetes clusters more than doubled compute capacity, and migrated-service traffic had grown 82% since March. Incidents included shared database overload from large migration queries, unsafe database routing changes that caused two write outages, reconnect bursts that saturated network links, and a regional Azure network disruption that cascaded into GitHub Actions failures. Other events involved overloaded event-streaming servers, an invalid Copilot model-provider credential, and a saturated database connection pool. Mitigations included batching importer queries, stronger routing validation, connection and retry controls, and improved monitoring. East US 3 was about a week behind plan, with its first validated traffic ramp targeted for the first week of December.

### Source excerpt

In October, we experienced eight incidents that resulted in degraded performance across GitHub services. The post GitHub availability report: October 2026 appeared first on The GitHub Blog.

## Hackers compromise 4,800 GitHub accounts to steal cloud credentials

DevFeed: [Hackers compromise 4,800 GitHub accounts to steal cloud credentials](<https://devfeed.tech/articles/hackers-compromise-4-800-github-accounts-to-steal-cloud-credentials-130986.md>)

Original publisher: [Read original article](<https://www.bleepingcomputer.com/news/security/hackers-compromise-4-800-github-accounts-to-steal-cloud-credentials/>)

Author: Bill Toulas

Published: 2026-11-12T22:25:30Z

Content type: news

Language: en

Sources: [BleepingComputer](<https://devfeed.tech/sources/bleepingcomputer.md>)

Topics: [Credential theft](<https://devfeed.tech/topics/credential-theft.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [account takeover](<https://devfeed.tech/topics/account-takeover.md>), [CI/CD secrets management](<https://devfeed.tech/topics/ci-cd-secrets-management.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [malicious packages](<https://devfeed.tech/topics/malicious-packages.md>), [npm security](<https://devfeed.tech/topics/npm-security.md>), [self-hosted runner](<https://devfeed.tech/topics/self-hosted-runner.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [actions](<https://devfeed.tech/tags/actions.md>), [ai](<https://devfeed.tech/tags/ai.md>), [anthropic](<https://devfeed.tech/tags/anthropic.md>), [aws](<https://devfeed.tech/tags/aws.md>), [azure](<https://devfeed.tech/tags/azure.md>), [campaign](<https://devfeed.tech/tags/campaign.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [compromise](<https://devfeed.tech/tags/compromise.md>), [computer-help](<https://devfeed.tech/tags/computer-help.md>), [computer-security](<https://devfeed.tech/tags/computer-security.md>), [computers](<https://devfeed.tech/tags/computers.md>), [copilot](<https://devfeed.tech/tags/copilot.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [cursor](<https://devfeed.tech/tags/cursor.md>), [docker](<https://devfeed.tech/tags/docker.md>), [environment-variables](<https://devfeed.tech/tags/environment-variables.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [google-cloud-platform](<https://devfeed.tech/tags/google-cloud-platform.md>), [infosec](<https://devfeed.tech/tags/infosec.md>), [infosec-computer-security](<https://devfeed.tech/tags/infosec-computer-security.md>), [linux](<https://devfeed.tech/tags/linux.md>), [mac](<https://devfeed.tech/tags/mac.md>), [malware](<https://devfeed.tech/tags/malware.md>), [malware-removal](<https://devfeed.tech/tags/malware-removal.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>), [repositories](<https://devfeed.tech/tags/repositories.md>), [secrets](<https://devfeed.tech/tags/secrets.md>), [security](<https://devfeed.tech/tags/security.md>), [spyware](<https://devfeed.tech/tags/spyware.md>), [support](<https://devfeed.tech/tags/support.md>), [tech-support](<https://devfeed.tech/tags/tech-support.md>), [technical-support](<https://devfeed.tech/tags/technical-support.md>), [virus](<https://devfeed.tech/tags/virus.md>), [virus-removal](<https://devfeed.tech/tags/virus-removal.md>), [wfx-loot](<https://devfeed.tech/tags/wfx-loot.md>), [windows](<https://devfeed.tech/tags/windows.md>)

### AI overview

The wfx-loot campaign used credentials from 4,837 compromised GitHub accounts to probe 61,764 repositories for write access; researchers confirmed secret theft from at least 1,835 targets. The attackers disguised pull requests as dependency audit notes, then injected a credential-stealing script through GitHub Actions workflows or npm install hooks. It sought GitHub and cloud tokens, developer and infrastructure secrets, and AI-service credentials, and could exchange GitHub OIDC tokens for temporary AWS, Azure, and Google Cloud sessions. Collected data was sent to attacker-controlled servers; changes and logs were then removed in under a minute. Automated publishing also placed malicious releases in Packagist and a Go module. Aikido advises checking for the wfx-docs branch, probe pull requests, and workflow-run gaps; where execution is confirmed, rotate all secrets and cloud roles available to affected workflows.

### Source excerpt

A new campaign dubbed 'wfx-loot' has unfolded on GitHub where threat actors used 4,837 compromised accounts to probe 61,764 repositories, open pull requests, and push secrets-stealing malware. [...]

## Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret Stealing Malware Via GitHub Actions & npm

DevFeed: [Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret Stealing Malware Via GitHub Actions & npm](<https://devfeed.tech/articles/thousands-of-github-accounts-hijacked-with-wfx-loot-ci-secret-stealing-malware-via-github-actions-npm-131777.md>)

Original publisher: [Read original article](<https://www.ox.security/blog/thousands-of-github-accounts-hijacked-with-wfx-loot-ci-secret-stealing-malware-via-github-actions-npm/>)

Author: Moshe Siman Tov Bustan

Published: 2026-11-12T17:35:37Z

Content type: news

Language: en

Sources: [OX Security](<https://devfeed.tech/sources/ox-security.md>)

Topics: [Credential theft](<https://devfeed.tech/topics/credential-theft.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [npm](<https://devfeed.tech/topics/npm.md>), [npm security](<https://devfeed.tech/topics/npm-security.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [campaign](<https://devfeed.tech/tags/campaign.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [malware](<https://devfeed.tech/tags/malware.md>), [npm](<https://devfeed.tech/tags/npm.md>), [research](<https://devfeed.tech/tags/research.md>), [secret](<https://devfeed.tech/tags/secret.md>), [security](<https://devfeed.tech/tags/security.md>), [stealer](<https://devfeed.tech/tags/stealer.md>), [supply-chain](<https://devfeed.tech/tags/supply-chain.md>), [wfx-loot](<https://devfeed.tech/tags/wfx-loot.md>)

### AI overview

OX Security describes an ongoing campaign in which attackers used 4,837 hijacked GitHub accounts to probe repositories, inject a roughly 1,500-line shell script through GitHub Actions workflows or npm install hooks, then quickly revert commits and delete workflow runs and logs. The script sought GitHub, cloud, package registry, Kubernetes, Vault and AI credentials; at least 1,806 repositories reportedly ran it and exfiltrated secrets. Exfiltration shifted from HTTP servers to Telegram, so blocking known IP addresses alone may not suffice. The article recommends searching for the named pull request, branch and commit patterns; rotating secrets and revoking reachable tokens if malicious code landed; and checking cloud identity and role configurations for persistence. A probe pull request alone is treated as evidence that its submitting account is compromised. The campaign was still active in the reported observations, and private repositories and non-default branches were not visible in the counts.

### Source excerpt

Threat actors used thousands of hijacked GitHub accounts to inject a self-erasing CI secret stealer into tens of thousands of repositories, stealing cloud, package registry and AI credentials Overview OX Security researchers are tracking a large-scale supply chain campaign, dubbed wfx-loot, in which threat actors used 4,837 hijacked GitHub accounts to push a CI secret [...] The post Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret Stealing Malware Via GitHub Actions & npm appeared first on OX Security.

## Attacker Targets 60,000 GitHub Repositories in Credential Theft Campaign

DevFeed: [Attacker Targets 60,000 GitHub Repositories in Credential Theft Campaign](<https://devfeed.tech/articles/attacker-targets-60-000-github-repositories-in-credential-theft-campaign-130468.md>)

Original publisher: [Read original article](<https://www.securityweek.com/attacker-targets-60000-github-repositories-in-credential-theft-campaign/>)

Author: Eduard Kovacs

Published: 2026-11-12T13:39:03Z

Content type: news

Language: en

Sources: [SecurityWeek](<https://devfeed.tech/sources/securityweek.md>)

Topics: [Credential theft](<https://devfeed.tech/topics/credential-theft.md>), [credential-based attacks](<https://devfeed.tech/topics/credential-based-attacks.md>), [Cybercrime](<https://devfeed.tech/topics/cybercrime.md>), [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [GitHub](<https://devfeed.tech/topics/github.md>)

Tags: [actions](<https://devfeed.tech/tags/actions.md>), [ai](<https://devfeed.tech/tags/ai.md>), [aikido-security](<https://devfeed.tech/tags/aikido-security.md>), [application-security](<https://devfeed.tech/tags/application-security.md>), [aws](<https://devfeed.tech/tags/aws.md>), [azure](<https://devfeed.tech/tags/azure.md>), [bot](<https://devfeed.tech/tags/bot.md>), [breach](<https://devfeed.tech/tags/breach.md>), [bug](<https://devfeed.tech/tags/bug.md>), [campaign](<https://devfeed.tech/tags/campaign.md>), [changes](<https://devfeed.tech/tags/changes.md>), [ci](<https://devfeed.tech/tags/ci.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [code](<https://devfeed.tech/tags/code.md>), [commits](<https://devfeed.tech/tags/commits.md>), [credential-theft](<https://devfeed.tech/tags/credential-theft.md>), [data-theft](<https://devfeed.tech/tags/data-theft.md>), [github](<https://devfeed.tech/tags/github.md>), [repositories](<https://devfeed.tech/tags/repositories.md>), [secret](<https://devfeed.tech/tags/secret.md>), [stealer](<https://devfeed.tech/tags/stealer.md>), [supply-chain-security](<https://devfeed.tech/tags/supply-chain-security.md>), [wfx-loot](<https://devfeed.tech/tags/wfx-loot.md>)

### AI overview

The wfx-loot campaign used stolen tokens from roughly 4,800 accounts to probe 61,764 GitHub repositories with pull requests. Those requests did not deploy malware by themselves: the attacker added credential-stealing code where repository permissions and configuration allowed it. Aikido found signs it ran in more than 1,800 repositories; SafeDep counted malicious commits in 8,093 public repositories, which does not establish successful execution. The code was placed in GitHub Actions workflows, CI shell scripts, and npm install hooks, and sought GitHub tokens, repository secrets, cloud credentials, and AI service keys. It could also read Actions runner memory and was designed to expand access and persist in AWS and Azure. The attacker often reverted changes and deleted workflow runs. If the malware executed, Aikido advised assuming accessible secrets were compromised; organizations were advised to revoke tokens, rotate secrets, and check cloud environments for unauthorized changes.

### Source excerpt

Using thousands of hijacked accounts, the wfx-loot campaign planted a CI secret stealer that ran in over 1,800 GitHub repositories. The post Attacker Targets 60,000 GitHub Repositories in Credential Theft Campaign appeared first on SecurityWeek.

## Avrea's Faster Runners for GitHub Actions Reflect How AI Coding Is Changing CI

DevFeed: [Avrea's Faster Runners for GitHub Actions Reflect How AI Coding Is Changing CI](<https://devfeed.tech/articles/avrea-s-faster-runners-for-github-actions-reflect-how-ai-coding-is-changing-ci-130595.md>)

Original publisher: [Read original article](<https://hackernoon.com/avreas-faster-runners-for-github-actions-reflect-how-ai-coding-is-changing-ci?source=rss>)

Author: Ishan Pandey

Published: 2026-11-12T11:23:29Z

Content type: news

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [CI/CD](<https://devfeed.tech/topics/cicd.md>), [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [Cache](<https://devfeed.tech/topics/cache.md>), [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-and-ml](<https://devfeed.tech/tags/ai-and-ml.md>), [ai-coding-agents](<https://devfeed.tech/tags/ai-coding-agents.md>), [avrea](<https://devfeed.tech/tags/avrea.md>), [build](<https://devfeed.tech/tags/build.md>), [caching](<https://devfeed.tech/tags/caching.md>), [ci](<https://devfeed.tech/tags/ci.md>), [ci-cd-pipelines](<https://devfeed.tech/tags/ci-cd-pipelines.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [good-company](<https://devfeed.tech/tags/good-company.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [technology](<https://devfeed.tech/tags/technology.md>)

### AI overview

AI coding agents are increasing CI workload, making build speed, repeated runs, and failure recovery practical bottlenecks. Teams using GitHub Actions can keep their workflows and switch to managed third-party runners, often by changing a runner label. Avrea combines faster hardware with caches for dependencies, Docker layers, build outputs, checkouts, and named build tools; it claims up to 2x faster builds from hardware and 10x with cache hits. RunsOn's November 2026 benchmark ranks Avrea first on tested ARM sizes and generally behind Namespace on x86, though Depot is absent and RunsOn is a competitor. Avrea offers job-level resource data, searchable logs, SSH debugging, and beta AI failure analysis; its own CI engine is also in beta, and the service supports GitHub Actions only. Managed runners reduce operational work compared with self-hosting, which offers control and inexpensive compute but requires teams to provision, patch, secure, and scale machines. Actual savings depend on runner size, duration, cache effectiveness, and operational costs; Avrea's price and speed figures are company claims.

### Source excerpt

AI coding agents are shipping more code than ever. See how faster GitHub Actions runners with smart caching help teams build up to 10x faster for less.

## Check your GitHub repos: A secret stealer hit tens of thousands of them

DevFeed: [Check your GitHub repos: A secret stealer hit tens of thousands of them](<https://devfeed.tech/articles/check-your-github-repos-a-secret-stealer-hit-tens-of-thousands-of-them-130128.md>)

Original publisher: [Read original article](<https://www.helpnetsecurity.com/2026/11/12/wfx-loot-github-actions-secret-stealer/>)

Author: Mirko Zorz

Published: 2026-11-12T09:24:32Z

Content type: news

Language: en

Sources: [Help Net Security](<https://devfeed.tech/sources/help-net-security.md>)

Topics: [Credential theft](<https://devfeed.tech/topics/credential-theft.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [Secret Scanning](<https://devfeed.tech/topics/secret-scanning.md>)

Tags: [aws](<https://devfeed.tech/tags/aws.md>), [azure](<https://devfeed.tech/tags/azure.md>), [devsecops](<https://devfeed.tech/tags/devsecops.md>), [don-t-miss](<https://devfeed.tech/tags/don-t-miss.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [github-credentials](<https://devfeed.tech/tags/github-credentials.md>), [hot-stuff](<https://devfeed.tech/tags/hot-stuff.md>), [malware](<https://devfeed.tech/tags/malware.md>), [news](<https://devfeed.tech/tags/news.md>), [repositories](<https://devfeed.tech/tags/repositories.md>), [secrets](<https://devfeed.tech/tags/secrets.md>), [supply-chain-compromise](<https://devfeed.tech/tags/supply-chain-compromise.md>), [threat-intelligence](<https://devfeed.tech/tags/threat-intelligence.md>), [threats](<https://devfeed.tech/tags/threats.md>), [wfx-loot](<https://devfeed.tech/tags/wfx-loot.md>)

### AI overview

A stolen GitHub token can expose every repository its owner can write to: Aikido counted probe pull requests in 61,764 repositories, with more than 1,800 cases where the wfx-loot payload ran and sent credentials to the attacker. The malware injects a workflow script, then removes it and its logs within about a minute. It targets GitHub Actions secrets, cloud and SSH credentials, shell histories, and AI tool tokens, and can establish cloud access that survives secret rotation through changed AWS trust policies or Azure federated credentials. Check for a wfx-docs branch, the probe pull request, or commits titled "ci: refresh build cache," "chore: add ci helper," or "chore: add dependency audit workflow." If the payload ran, treat reachable secrets and cloud roles as compromised; also locate and remove persistent cloud trust changes. Missing artifacts do not establish safety because data was sent directly to attacker servers.

### Source excerpt

A threat actor using stolen GitHub credentials has pushed a credential-stealing payload into tens of thousands of repositories since November 10. In more than 1,800 of them, the malware ran and shipped GitHub Actions secrets and cloud credentials to the attacker. Aikido spotted the campaign and named it wfx-loot. The name comes from the attacker's own labels, "wfx" for the malware and "loot" for what it steals. Aikido counted 4,837 compromised accounts opening probe pull ... More -> The post Check your GitHub repos: A secret stealer hit tens of thousands of them appeared first on Help Net Security.

## wfx-loot: Stolen GitHub tokens pushed a CI secret stealer into 60,000+ repositories (November 2026)

DevFeed: [wfx-loot: Stolen GitHub tokens pushed a CI secret stealer into 60,000+ repositories (November 2026)](<https://devfeed.tech/articles/wfx-loot-stolen-github-tokens-pushed-a-ci-secret-stealer-into-60-000-repositories-november-2026-131801.md>)

Original publisher: [Read original article](<https://www.chainguard.dev/unchained/wfx-loot-stolen-github-tokens-pushed-a-ci-secret-stealer-into-60-000-repositories-november-2026>)

Published: 2026-11-12T00:00:00Z

Content type: article

Language: en

Sources: [Chainguard: Unchained](<https://devfeed.tech/sources/chainguard-unchained.md>)

Topics: [software supply-chain attack](<https://devfeed.tech/topics/software-supply-chain-attack.md>), [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [chainguard actions](<https://devfeed.tech/topics/chainguard-actions.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [self-hosted runner](<https://devfeed.tech/topics/self-hosted-runner.md>), [HashiCorp Vault](<https://devfeed.tech/topics/hashicorp-vault.md>), [GitHub Copilot](<https://devfeed.tech/topics/github-copilot.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [access-tokens](<https://devfeed.tech/tags/access-tokens.md>), [attack](<https://devfeed.tech/tags/attack.md>), [ci](<https://devfeed.tech/tags/ci.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [github](<https://devfeed.tech/tags/github.md>), [november-2026](<https://devfeed.tech/tags/november-2026.md>), [secret](<https://devfeed.tech/tags/secret.md>), [stealer](<https://devfeed.tech/tags/stealer.md>), [supply-chain](<https://devfeed.tech/tags/supply-chain.md>), [supply-chain-attack](<https://devfeed.tech/tags/supply-chain-attack.md>), [tokens](<https://devfeed.tech/tags/tokens.md>), [wfx](<https://devfeed.tech/tags/wfx.md>), [wfx-loot](<https://devfeed.tech/tags/wfx-loot.md>)

### AI overview

The wfx campaign used stolen GitHub credentials to inject a CI secret stealer into repositories those accounts could write to. Aikido counted 61,764 repositories with probe pull requests, while SafeDep counted 8,093 receiving malicious commits; execution was confirmed in more than 1,800 repositories. The payload collected CI secrets, tokens, cloud credentials, and runner memory, then could create cloud persistence that survives secret rotation. To investigate, search for the wfx-docs branch, the "docs: dependency audit notes" pull request, injected workflow or install-hook files, and missing workflow run numbers. If it ran, revoke the compromised GitHub credential, rotate all credentials accessible to workflows, remove injected files, restore AWS trust policies and delete unauthorized Azure federated credentials, then audit cloud activity. The excerpt also describes Chainguard Checks as keeping real credentials outside its managed CI microVMs and using short-lived OIDC tokens with provider-side credential substitution.

### Source excerpt

The wfx supply chain attack compromised thousands of GitHub repositories. See how it works, what credentials it steals, and how to stay protected.

## Self-Service Namespace Onboarding on Amazon EKS: Automating Access Entries and RBAC with GitHub...

DevFeed: [Self-Service Namespace Onboarding on Amazon EKS: Automating Access Entries and RBAC with GitHub...](<https://devfeed.tech/articles/self-service-namespace-onboarding-on-amazon-eks-automating-access-entries-and-rbac-with-github-127576.md>)

Original publisher: [Read original article](<https://blog.devops.dev/self-service-namespace-onboarding-on-amazon-eks-automating-access-entries-and-rbac-with-github-74f0347e71e2?source=rss----33f8b2d9a328---4>)

Author: Oleh Adam Dubnytskyy

Published: 2026-11-10T09:42:12Z

Content type: tutorial

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [rbac](<https://devfeed.tech/topics/rbac.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [AWS Security Token Service](<https://devfeed.tech/topics/aws-security-token-service.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [self-service](<https://devfeed.tech/topics/self-service.md>), [internal developer platform automation](<https://devfeed.tech/topics/internal-developer-platform-automation.md>), [GitHub](<https://devfeed.tech/topics/github.md>)

Tags: [admin](<https://devfeed.tech/tags/admin.md>), [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [amazon-web-services](<https://devfeed.tech/tags/amazon-web-services.md>), [api](<https://devfeed.tech/tags/api.md>), [api-server](<https://devfeed.tech/tags/api-server.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [automation](<https://devfeed.tech/tags/automation.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-eks](<https://devfeed.tech/tags/aws-eks.md>), [ci](<https://devfeed.tech/tags/ci.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [devops](<https://devfeed.tech/tags/devops.md>), [eks](<https://devfeed.tech/tags/eks.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [iam](<https://devfeed.tech/tags/iam.md>), [job](<https://devfeed.tech/tags/job.md>), [keys](<https://devfeed.tech/tags/keys.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [onboarding](<https://devfeed.tech/tags/onboarding.md>), [rbac](<https://devfeed.tech/tags/rbac.md>), [self-service](<https://devfeed.tech/tags/self-service.md>)

### AI overview

The excerpt describes namespace onboarding on Amazon EKS as two coordinated permission updates: an EKS access policy scope and Kubernetes RBAC. GitHub Actions authenticates through OIDC and temporary IAM role credentials. The EKS authorizer and RBAC authorizer can each allow a request, so effective permissions are their union; a restrictive custom RBAC role cannot narrow permissions already granted by a broader managed policy. The proposed setup uses separate workflows: one applies ClusterRoles and per-namespace RoleBindings, while another updates the access entry's namespace scope from files in a namespaces directory. The scripts validate namespace names, reject empty desired scopes, skip unchanged access-policy updates, and optionally prune stale managed RoleBindings. The excerpt notes that RBAC synchronization requires cluster-scoped rights and that missing namespaces are skipped with a warning before the workflow reports an error. The supplied text ends after describing this implementation and its pull request workflow.

### Source excerpt

Self-Service Namespace Onboarding on Amazon EKS: Automating Access Entries and RBAC with GitHub ActionsTwo authorization layers on Amazon EKS Every call my pipeline makes to the cluster's Kubernetes API server passes through two authorizers: Kubernetes RBAC and EKS access policies. Authentication: the access entry says who you are The pipeline never holds long-lived AWS keys. A GitHub Actions job gets an OIDC token, exchanges it for temporary credentials of an IAM role, and calls the cluster with them. More details on how it works can be seen here. Layer 1: Kubernetes RBAC RBAC is the standard Kubernetes model: Roles and ClusterRoles define rules, and RoleBindings attach them to a user or group. These objects live inside the cluster. You can write any rule you need, including rules for custom resources such as KEDA ScaledObject. Layer 2: EKS access policies Access policies are permission sets that AWS manages and that you attach to an access entry through the EKS API. They mirror the Kubernetes user-facing roles: AmazonEKSEditPolicy corresponds to edit, AmazonEKSAdminPolicy to admin, and so on. Each association has a scope: the whole cluster (type=cluster) or a list of namespaces (type=namespace). You can't modify an access policy or create your own. When the managed policies don't fit, more control can be configured by leveraging Kubernetes RBAC objects instead. How the two layers combine The API server chains its authorizers. The RBAC authorizer runs first and returns immediately if it allows the request. If RBAC has no opinion, the request goes to the EKS authorizer, which checks the access policies. If neither allows it, the request is denied. The access entry only establishes who the caller is; RBAC and access policies each get one chance to allow the request. Both authorizers can only allow or pass, so the effective permissions of ci-github-actions in a namespace are the union of both layers. That has two consequences for the automation: Onboarding a namespace

## Monitor your CI performance using Sentry

DevFeed: [Monitor your CI performance using Sentry](<https://devfeed.tech/articles/monitor-your-ci-performance-using-sentry-129748.md>)

Original publisher: [Read original article](<https://blog.sentry.io/monitor-ci-performance-sentry/>)

Author: Phil Niedertscheider; Ricardo Oliveira; Armen Zambrano G.

Published: 2026-11-10T09:00:00Z

Content type: tutorial

Language: en

Sources: [Sentry](<https://devfeed.tech/sources/sentry-blog.md>)

Topics: [CI/CD](<https://devfeed.tech/topics/cicd.md>), [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>)

Tags: [automated-testing](<https://devfeed.tech/tags/automated-testing.md>), [build](<https://devfeed.tech/tags/build.md>), [caching](<https://devfeed.tech/tags/caching.md>), [ci](<https://devfeed.tech/tags/ci.md>), [cli](<https://devfeed.tech/tags/cli.md>), [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [custom-dashboard](<https://devfeed.tech/tags/custom-dashboard.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [dashboards](<https://devfeed.tech/tags/dashboards.md>), [distributed-tracing](<https://devfeed.tech/tags/distributed-tracing.md>), [explore](<https://devfeed.tech/tags/explore.md>), [explorer](<https://devfeed.tech/tags/explorer.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [monitor](<https://devfeed.tech/tags/monitor.md>), [net](<https://devfeed.tech/tags/net.md>), [net-sdk](<https://devfeed.tech/tags/net-sdk.md>), [sentry](<https://devfeed.tech/tags/sentry.md>), [traces](<https://devfeed.tech/tags/traces.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

The article reports that representing GitHub Actions jobs as Sentry traces helped the Sentry .NET SDK team cut one workflow's duration by 71% (about 1 hour 23 minutes to 24 minutes); a dashboard comparison across runs showed an overall reduction of about 64%. To set up collection, create a Sentry project, create a private `.sentry` repository for each GitHub owner, add `sentry_config.ini` with the project DSN, and install the GitHub App with access to that repository and the workflows to monitor. The app reads run metadata and the configuration file, not source code, then sends completed jobs as traces. Sentry Explore, dashboards, and CLI access can help inspect durations and p50/p90 trends. The app is experimental, and ingested traces count toward span quota (or transaction quota on older plans).

### Source excerpt

We turned GitHub Actions workflows into Sentry traces to find slow CI steps and cut run time. Here's how to set it up for your own workflows.

## Secret scanning detects secrets in GitHub Actions workflow logs

DevFeed: [Secret scanning detects secrets in GitHub Actions workflow logs](<https://devfeed.tech/articles/secret-scanning-detects-secrets-in-github-actions-workflow-logs-124115.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2026-11-09-secret-scanning-detects-secrets-in-github-actions-workflow-logs>)

Author: Allison

Published: 2026-11-09T09:01:37Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [Secret Scanning](<https://devfeed.tech/topics/secret-scanning.md>), [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [GitHub](<https://devfeed.tech/topics/github.md>)

Tags: [actions](<https://devfeed.tech/tags/actions.md>), [application-security](<https://devfeed.tech/tags/application-security.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [improvement](<https://devfeed.tech/tags/improvement.md>), [logs](<https://devfeed.tech/tags/logs.md>), [preview](<https://devfeed.tech/tags/preview.md>), [scanning](<https://devfeed.tech/tags/scanning.md>), [secret](<https://devfeed.tech/tags/secret.md>), [secret-scanning](<https://devfeed.tech/tags/secret-scanning.md>), [secrets](<https://devfeed.tech/tags/secrets.md>), [workflow](<https://devfeed.tech/tags/workflow.md>)

### AI overview

GitHub's public preview scans completed Actions workflow logs for supported provider secret patterns and adds findings to the repository's secret scanning alerts, with links to the logs. Validity checks run for supported secret types, and alerts remain after logs are deleted. Enterprise owners can enable the policy in GitHub Enterprise Cloud settings; it is off by default and applies only to licensed repositories where secret scanning is enabled. Only runs completed after activation are scanned. Generic and custom patterns, AI-detected secrets, and secrets masked by Actions are excluded. Preview alerts do not trigger notifications, so repositories must check the alert list directly.

### Source excerpt

GitHub secret scanning now detects secrets in GitHub Actions workflow logs, in addition to issues, wikis, discussions, and pull requests. Actions workflow log scanning is available in public preview. How... The post Secret scanning detects secrets in GitHub Actions workflow logs appeared first on The GitHub Blog.

## Releasing Ruby Gems with OIDC and GitHub Actions

DevFeed: [Releasing Ruby Gems with OIDC and GitHub Actions](<https://devfeed.tech/articles/releasing-ruby-gems-with-oidc-and-github-actions-122503.md>)

Original publisher: [Read original article](<https://code.dblock.org/2026/11/07/releasing-ruby-gems-with-oidc-and-github-actions.html>)

Author: Daniel Doubrovkine (dblock@dblock.org)

Published: 2026-11-07T00:00:00Z

Content type: tutorial

Language: en

Sources: [Daniel Doubrovkine](<https://devfeed.tech/sources/daniel-doubrovkine.md>)

Topics: [project release](<https://devfeed.tech/topics/project-release.md>), [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [rubygems](<https://devfeed.tech/topics/rubygems.md>), [Ruby](<https://devfeed.tech/topics/ruby.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>)

Tags: [github-actions](<https://devfeed.tech/tags/github-actions.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [ruby](<https://devfeed.tech/tags/ruby.md>)

### AI overview

ruby-gem-release automates Ruby gem release bookkeeping through Ruby tasks and a reusable GitHub Actions workflow. RubyGems Trusted Publishing provides short-lived credentials, avoiding a stored RubyGems API key; after setup, collaborators with write access can dispatch releases. The example reads the version from a Ruby constant, dates the changelog before publishing, then increments the version and adds a "Next" section. It supports Intridea and Keep a Changelog formats. First publication requires configuring a trusted publisher and passing the numeric RubyGems account ID; later releases omit that input. For customization, Ruby callbacks expose steps such as changelog preparation, building and publishing the gem, Git tagging, and GitHub release creation as ordinary methods that can be tested.

### Source excerpt

The traditional approach for automating Ruby gem releases is to use release-gem. It's super simple. You can also build upon it when you need something beyond the plain rake release, such as updating a CHANGELOG.md, by rolling miles of brittle GitHub Actions YAML and shell script AI slop. Instead, I've been asking AI to follow a hand-crafted RELEASING.md. It can run tests, date CHANGELOG.md, ask me for a RubyGems OTP, make the release, increment the version of the next developer iteration. This works well. Still, AI is a very blunt tool for something that should be mechanized. Therefore, I built ruby-gem-release to automate all release bookkeeping in Ruby in an extensible workflow. The release runs in GitHub Actions. RubyGems Trusted Publishing supplies short-lived credentials, so there is no RubyGems API key to store in GitHub secrets or share with other maintainers. After setup, collaborators with write access can dispatch releases too. As an example, I added it to ruby-link-checker. Here's the Rakefile addition: require 'ruby-gem-release/workflow/ruby_gem' require 'ruby-gem-release/changelog' RubyGemRelease::Workflow::RubyGem.new( version: RubyGemRelease::Version::RubyConstant.new(path: 'lib/ruby-link-checker/version.rb', constant: 'VERSION'), changelog: RubyGemRelease::Changelog::Intridea.new(placeholder: '* Your contribution here.') ).install_tasks The version strategy reads a constant from lib/ruby-link-checker/version.rb: module LinkChecker VERSION = '0.5.0'.freeze end The CHANGELOG.md in this project is in the Intridea style. The gem also supports Keep a Changelog. Before publishing 0.5.0 the CHANGELOG.md is updated with a date. After publishing, the VERSION constant is incremented to 0.5.1, and CHANGELOG.md is updated with a Next section. Add .github/workflows/release.yml to call the reusable release workflow. The optional rubygems-owner input accepts your numeric RubyGems account ID when publishing a new gem for the first time: name: Release on: workflow_di

## Beyond SHA pinning: Why immutability isn't provenance in GitHub Actions

DevFeed: [Beyond SHA pinning: Why immutability isn't provenance in GitHub Actions](<https://devfeed.tech/articles/beyond-sha-pinning-why-immutability-isn-t-provenance-in-github-actions-122069.md>)

Original publisher: [Read original article](<https://platformengineering.org/blog/beyond-sha-pinning-why-immutability-isnt-provenance-in-github-actions>)

Author: Erika Heidi

Published: 2026-11-06T20:11:44Z

Content type: article

Language: en

Sources: [Platform Engineering Blog](<https://devfeed.tech/sources/platform-engineering-blog.md>)

Topics: [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [chainguard actions](<https://devfeed.tech/topics/chainguard-actions.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [software artifact signing](<https://devfeed.tech/topics/software-artifact-signing.md>), [sigstore](<https://devfeed.tech/topics/sigstore.md>)

Tags: [actions](<https://devfeed.tech/tags/actions.md>), [can](<https://devfeed.tech/tags/can.md>), [cd](<https://devfeed.tech/tags/cd.md>), [ci](<https://devfeed.tech/tags/ci.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [commits](<https://devfeed.tech/tags/commits.md>), [doesn-t](<https://devfeed.tech/tags/doesn-t.md>), [exploit](<https://devfeed.tech/tags/exploit.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [immutability](<https://devfeed.tech/tags/immutability.md>), [isn-t](<https://devfeed.tech/tags/isn-t.md>), [learn](<https://devfeed.tech/tags/learn.md>), [platform](<https://devfeed.tech/tags/platform.md>), [platform-teams](<https://devfeed.tech/tags/platform-teams.md>), [provenance](<https://devfeed.tech/tags/provenance.md>), [supply-chain](<https://devfeed.tech/tags/supply-chain.md>), [take](<https://devfeed.tech/tags/take.md>), [teams](<https://devfeed.tech/tags/teams.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

SHA pinning prevents a GitHub Action's reference from following a moved tag, but it does not establish who authored the pinned commit, whether it belongs to the intended project, or what a container action downloads at runtime. The article describes "imposter commits" reachable through an upstream repository URL despite existing only in a fork, and says such a commit could pass SHA format enforcement. It recommends pinning every action and reviewing automated pin updates, while treating provenance as a separate requirement. GitHub's immutable releases lock tags and assets and include Sigstore attestations, but adoption is opt-in for action maintainers. Workflow lock files pin actions and transitive dependencies and require commits to exist on source branches; they were described as in public preview. Other approaches include internal mirrors, provenance verification, and curated catalogs, each requiring ongoing maintenance or trust-policy decisions. The article presents Chainguard Actions as a curated, rebuilt catalog, and advises shrinking the attack surface with minimal hardened images.

### Source excerpt

Learn why SHA pinning in GitHub Actions doesn't guarantee provenance, how imposter commits exploit CI/CD workflows, and key steps platform teams can take to secure their supply chain.

## GitHub Actions Lockfiles Reach GA to Secure Workflow Dependencies

DevFeed: [GitHub Actions Lockfiles Reach GA to Secure Workflow Dependencies](<https://devfeed.tech/articles/github-actions-lockfiles-reach-ga-to-secure-workflow-dependencies-120954.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/11/github-actions-lockfiles-ga/>)

Author: Claudio Masolo

Published: 2026-11-06T09:00:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [GitHub CLI extension](<https://devfeed.tech/topics/gh-extension.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [actions](<https://devfeed.tech/tags/actions.md>), [branch](<https://devfeed.tech/tags/branch.md>), [ci](<https://devfeed.tech/tags/ci.md>), [circleci](<https://devfeed.tech/tags/circleci.md>), [circleci-orbs](<https://devfeed.tech/tags/circleci-orbs.md>), [cli](<https://devfeed.tech/tags/cli.md>), [data-residency](<https://devfeed.tech/tags/data-residency.md>), [dependabot](<https://devfeed.tech/tags/dependabot.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [dependency-management](<https://devfeed.tech/tags/dependency-management.md>), [devops](<https://devfeed.tech/tags/devops.md>), [feature](<https://devfeed.tech/tags/feature.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [github-actions-lockfiles-ga](<https://devfeed.tech/tags/github-actions-lockfiles-ga.md>), [news](<https://devfeed.tech/tags/news.md>), [october](<https://devfeed.tech/tags/october.md>), [preview](<https://devfeed.tech/tags/preview.md>), [public](<https://devfeed.tech/tags/public.md>), [tag](<https://devfeed.tech/tags/tag.md>), [workflow](<https://devfeed.tech/tags/workflow.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

GitHub Actions lockfiles make workflow runs use recorded commits for direct and transitive dependencies, even if referenced tags or branches later move. Teams generate and maintain `.github/workflows/actions.lock` with the `gh actions-lock` extension, can verify it in CI without changing files, and can have Dependabot update the lockfile alongside action version changes in one pull request. Admins can require lockfiles at enterprise, organization, or repository scope; adoption can proceed workflow by workflow. The feature is available on GitHub Enterprise Cloud, Enterprise Cloud with data residency, Team, and Free plans. Locking ensures commit consistency, not safety: teams still need to review dependencies when entries are created or updated, especially if Dependabot changes are auto-merged. The text contrasts this with guidance on other platforms that relies on manual SHA or digest pinning, policies against attack patterns, or immutable semantic-version registries; those approaches are described as not resolving transitive dependencies.

### Source excerpt

GitHub has made workflow dependency lockfiles for GitHub Actions generally available on October 28, 2026, two weeks after the feature entered public preview. Workflows can maintain clear tag and branch references. By Claudio Masolo

## GitHub Actions down? No problem. Green with Chainguard Checks.

DevFeed: [GitHub Actions down? No problem. Green with Chainguard Checks.](<https://devfeed.tech/articles/github-actions-down-no-problem-green-with-chainguard-checks-121996.md>)

Original publisher: [Read original article](<https://www.chainguard.dev/unchained/github-actions-down-no-problem-green-with-chainguard-checks>)

Published: 2026-11-06T00:00:00Z

Content type: article

Language: en

Sources: [Chainguard: Unchained](<https://devfeed.tech/sources/chainguard-unchained.md>)

Topics: [CI/CD](<https://devfeed.tech/topics/cicd.md>), [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [chainguard](<https://devfeed.tech/topics/chainguard.md>), [self-hosted runner](<https://devfeed.tech/topics/self-hosted-runner.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [actions](<https://devfeed.tech/tags/actions.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-development](<https://devfeed.tech/tags/agentic-development.md>), [agentic-workflows](<https://devfeed.tech/tags/agentic-workflows.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [auditing](<https://devfeed.tech/tags/auditing.md>), [automate](<https://devfeed.tech/tags/automate.md>), [automated](<https://devfeed.tech/tags/automated.md>), [chainguard](<https://devfeed.tech/tags/chainguard.md>), [chainguard-checks](<https://devfeed.tech/tags/chainguard-checks.md>), [ci](<https://devfeed.tech/tags/ci.md>), [faster](<https://devfeed.tech/tags/faster.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [github-actions-outages](<https://devfeed.tech/tags/github-actions-outages.md>), [outages](<https://devfeed.tech/tags/outages.md>)

### AI overview

Chainguard replaced GitHub Actions in a high-volume repository after growth to roughly 2,000 daily merges made Actions outages a bottleneck; self-hosted runners were also affected because the Actions control plane schedules work and reports status. Chainguard Checks runs each build and test in an isolated microVM, spans multiple cloud providers, retries failed jobs on fresh VMs, uses short-lived scoped identities, and limits network access to approved hosts. It selects checks by changed paths and reports results on pull requests, with a required check gating merges. Migration used parallel runs to compare results, staged rollouts with fallback, and a guard against new Actions workflows. The article reports steady merge rates through three October Actions incidents, about twice-as-fast image builds, and reduced compute for pull requests touching no packages. GitHub remains the source host and event and check interface, so GitHub.com outages can still affect the workflow; Checks is described as in beta.

### Source excerpt

GitHub Actions outages were slowing Chainguard down. Learn how we built and migrated to Chainguard Checks for faster, more resilient CI.

## Central Agentic Ops (CAO)

DevFeed: [Central Agentic Ops (CAO)](<https://devfeed.tech/articles/central-agentic-ops-cao-121418.md>)

Original publisher: [Read original article](<https://githubnext.com/projects/central-agentic-ops/>)

Published: 2026-11-05T00:00:00Z

Content type: article

Language: en

Sources: [GitHub Next](<https://devfeed.tech/sources/github-next.md>)

Topics: [GitHub Agentic Workflows](<https://devfeed.tech/topics/github-agentic-workflows.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ops](<https://devfeed.tech/tags/agentic-ops.md>), [agentic-workflows](<https://devfeed.tech/tags/agentic-workflows.md>), [monitor](<https://devfeed.tech/tags/monitor.md>), [ops](<https://devfeed.tech/tags/ops.md>), [repositories](<https://devfeed.tech/tags/repositories.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

Central Agentic Ops (CAO) is an early research prototype for governing shared agentic workflows across repositories. It brings activity, costs, outcomes, and review effort into one view so teams can decide what work is useful and when it should run. CAO governs whether and where work may run; Agentic Workflows, executed through GitHub Actions, govern how it runs. Teams can begin with bounded, read-only monitoring, then run one task in review mode, where proposed outputs go to a configured review destination before live outputs are explicitly authorized. Execution remains constrained by reviewed policy, repository permissions, declared safe outputs, and audit trails; pull requests still require human acceptance. CAO is not an all-purpose agent, and it governs only explicitly integrated workflows. Its recommendations group recurring failures for review, while choosing and dispatching valuable interventions remains research. The prototype supports several credential and hosting setups, but access, API limits, administrator help, GitHub plan limits, and dashboard visibility can constrain them. Its results may be stale, partial, or unavailable. The article describes research directions,

### Source excerpt

Monitor and govern agentic workflows across repositories

## Your GitHub Actions Cron Job Can Disappear Without Failing

DevFeed: [Your GitHub Actions Cron Job Can Disappear Without Failing](<https://devfeed.tech/articles/your-github-actions-cron-job-can-disappear-without-failing-116250.md>)

Original publisher: [Read original article](<https://hackernoon.com/your-github-actions-cron-job-can-disappear-without-failing?source=rss>)

Author: Malek Damiri

Published: 2026-11-04T10:00:02Z

Content type: tutorial

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [Slack](<https://devfeed.tech/topics/slack.md>), [GitHub](<https://devfeed.tech/topics/github.md>)

Tags: [actions](<https://devfeed.tech/tags/actions.md>), [airflow](<https://devfeed.tech/tags/airflow.md>), [alert](<https://devfeed.tech/tags/alert.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [automated](<https://devfeed.tech/tags/automated.md>), [bot](<https://devfeed.tech/tags/bot.md>), [branch](<https://devfeed.tech/tags/branch.md>), [bridge](<https://devfeed.tech/tags/bridge.md>), [cron](<https://devfeed.tech/tags/cron.md>), [data-engineering](<https://devfeed.tech/tags/data-engineering.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [github-actions-cron](<https://devfeed.tech/tags/github-actions-cron.md>), [github-actions-schedule](<https://devfeed.tech/tags/github-actions-schedule.md>), [github-actions-yaml](<https://devfeed.tech/tags/github-actions-yaml.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [qa](<https://devfeed.tech/tags/qa.md>), [reporting](<https://devfeed.tech/tags/reporting.md>), [scheduled](<https://devfeed.tech/tags/scheduled.md>), [scheduled-workflows](<https://devfeed.tech/tags/scheduled-workflows.md>), [slack](<https://devfeed.tech/tags/slack.md>), [workflow-monitoring](<https://devfeed.tech/tags/workflow-monitoring.md>), [workflow-reliability](<https://devfeed.tech/tags/workflow-reliability.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

GitHub Actions scheduled workflows can be delayed or silently dropped, so a daily report should check its data before posting and alert when no successful run appears. The excerpt recommends scheduling off the busy hour with an IANA timezone, testing QA rules, enabling manual dispatch, and using concurrency to prevent overlapping runs. Its report checks cover data freshness, whether driver totals reconcile, the size of the "other" category, and row counts; failed checks route the report to its owner. A Slack history check avoids duplicate posts after retries. A later watchdog can look for a successful run, but because it uses the same scheduler, it is only a second chance; the excerpt suggests an external heartbeat for more important reports. It recommends a more dependable scheduler when exact timing or frequent missed runs matter.

### Source excerpt

Learn how to make GitHub Actions scheduled workflows more reliable with automated QA, Slack reporting, duplicate prevention, and watchdog monitoring.

## GitInject: Real-World Prompt Injection Attacks in AI-Powered CI/CD Pipelines

DevFeed: [GitInject: Real-World Prompt Injection Attacks in AI-Powered CI/CD Pipelines](<https://devfeed.tech/articles/gitinject-real-world-prompt-injection-attacks-in-ai-powered-ci-cd-pipelines-113995.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2606.09935>)

Author: Jafar Isbarov, Umid Suleymanov, Ilia Shumailov, Murat Kantarcioglu

Published: 2026-11-03T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>)

Topics: [prompt injection](<https://devfeed.tech/topics/prompt-injection.md>), [ai security](<https://devfeed.tech/topics/ai-security.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [software supply-chain attack](<https://devfeed.tech/topics/software-supply-chain-attack.md>), [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>)

Tags: [actions](<https://devfeed.tech/tags/actions.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-powered](<https://devfeed.tech/tags/ai-powered.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [availability](<https://devfeed.tech/tags/availability.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [ci-cd-workflows](<https://devfeed.tech/tags/ci-cd-workflows.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [continuous-delivery](<https://devfeed.tech/tags/continuous-delivery.md>), [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [contribution](<https://devfeed.tech/tags/contribution.md>), [contributions](<https://devfeed.tech/tags/contributions.md>), [coverage](<https://devfeed.tech/tags/coverage.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [pipelines](<https://devfeed.tech/tags/pipelines.md>), [prompt-injection](<https://devfeed.tech/tags/prompt-injection.md>), [real-world](<https://devfeed.tech/tags/real-world.md>)

### AI overview

GitInject evaluates prompt injection in live, fully automated CI/CD workflows, where unmerged contributions can trigger AI agents with repository tools and credentials. The framework provisions ephemeral repositories and runs actual GitHub Actions workflows, capturing sandbox, credential, and permission behavior that simulated tool-call benchmarks may miss. Across eleven attack scenarios, five workflows, and four AI providers, each provider was susceptible to at least one high-severity attack in the tested configurations. The central weakness was structural: attacker-controlled configuration files could be loaded as operator-level instructions, potentially exposing credentials or corrupting review judgments. Two configuration-file attacks also replicated on GitLab and Hugging Face. The authors assessed workflow-level countermeasures and their coverage and utility tradeoffs; the supplied abstract does not specify which measures or tradeoffs.

### Source excerpt

arXiv:2606.09935v2 Announce Type: replace Abstract: AI agents are increasingly embedded in continuous integration and continuous delivery (CI/CD) workflows to autonomously review pull requests, triage issues, and maintain codebases. We study fully automated configurations in which external contributions invoke agents without prior human approval. Because these agents ingest untrusted content while operating with repository credentials and tools, prompt injection can have software supply chain consequences. We present GitInject, an open-source framework for evaluating prompt injection in live GitHub Actions workflows. Unlike benchmarks that simulate tool calls, GitInject provisions ephemeral repositories and executes actual workflows, exposing platform semantics such as sandbox constraints, credential handling, and permission boundaries. We use GitInject to evaluate eleven named attack scenarios across five workflows from four AI providers, covering configuration-file injection, credential exfiltration, judgment manipulation, and availability. Every provider is susceptible to at least one high-severity attack in the tested configurations. The most consequential vulnerabilities are structural: attacker-controlled configuration files from an unmerged contribution are loaded as operator-level instructions, allowing the agent--infrastructure interaction to expose credentials or corrupt review judgments. Two configuration-file attacks replicate on GitLab and Hugging Face as well as GitHub. We evaluate workflow-level countermeasures and show their coverage and utility tradeoffs. We release GitInject and all attack scenarios.

## Avrea is the fastest GitHub Actions runner in RunsOn's benchmark

DevFeed: [Avrea is the fastest GitHub Actions runner in RunsOn's benchmark](<https://devfeed.tech/articles/avrea-is-the-fastest-github-actions-runner-in-runson-s-benchmark-122840.md>)

Original publisher: [Read original article](<https://avrea.com/blog/avrea-runson-build-benchmark>)

Author: Hannu Valtonen

Published: 2026-11-03T00:00:00Z

Content type: news

Language: en

Sources: [Avrea Blog](<https://devfeed.tech/sources/avrea-blog.md>)

Topics: [Benchmark](<https://devfeed.tech/topics/benchmark.md>), [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [Bun](<https://devfeed.tech/topics/bun.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>)

Tags: [actions](<https://devfeed.tech/tags/actions.md>), [app](<https://devfeed.tech/tags/app.md>), [backend](<https://devfeed.tech/tags/backend.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [build](<https://devfeed.tech/tags/build.md>), [build-times](<https://devfeed.tech/tags/build-times.md>), [builds](<https://devfeed.tech/tags/builds.md>), [buildx](<https://devfeed.tech/tags/buildx.md>), [bun](<https://devfeed.tech/tags/bun.md>), [c](<https://devfeed.tech/tags/c.md>), [c-plus-plus](<https://devfeed.tech/tags/c-plus-plus.md>), [cache](<https://devfeed.tech/tags/cache.md>), [docker](<https://devfeed.tech/tags/docker.md>), [faster](<https://devfeed.tech/tags/faster.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [results](<https://devfeed.tech/tags/results.md>), [runner](<https://devfeed.tech/tags/runner.md>), [rust](<https://devfeed.tech/tags/rust.md>), [typescript](<https://devfeed.tech/tags/typescript.md>)

### AI overview

RunsOn's benchmark reports that Avrea's four-vCPU x64 runner completed three uncached builds faster and at lower estimated cost than GitHub's: PostHog's Docker build took 4m52s versus 12m53s, opencode's TypeScript checks 40s versus 1m52s, and spotify-player's Rust job 1m26s versus 3m33s. RunsOn sums median build times for its ranking and publishes methodology, code, and logs. For these three builds, it estimates $0.0625 on Avrea versus $0.2612 on GitHub; the per-minute rates cited are $0.008 and $0.012, respectively. The excerpt says Avrea supports Turborepo remote caching, sccache for Rust/C/C++, and colocated dependency caches for npm, pnpm, Yarn Classic, and Bun. It suggests trying the same workflow and commit on both providers, then rerunning on Avrea to observe caching effects. Results reflect the specified workloads and configurations.

### Source excerpt

Avrea leads RunsOn's 4-vCPU x64 build benchmark, completing Rust, TypeScript and Docker workloads 163% faster than GitHub. See all provider results.

## pull\_request\_target blocked by default December 2

DevFeed: [pull\_request\_target blocked by default December 2](<https://devfeed.tech/articles/pull-request-target-blocked-by-default-december-2-113833.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2026-11-02-pull_request_target-blocked-by-default-december-2>)

Author: Allison

Published: 2026-11-02T15:14:46Z

Content type: news

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [actions](<https://devfeed.tech/tags/actions.md>), [application-security](<https://devfeed.tech/tags/application-security.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [insights](<https://devfeed.tech/tags/insights.md>), [policy](<https://devfeed.tech/tags/policy.md>), [protection](<https://devfeed.tech/tags/protection.md>), [public](<https://devfeed.tech/tags/public.md>), [pull-request-target](<https://devfeed.tech/tags/pull-request-target.md>), [repositories](<https://devfeed.tech/tags/repositories.md>), [retired](<https://devfeed.tech/tags/retired.md>), [workflow](<https://devfeed.tech/tags/workflow.md>)

### AI overview

Starting December 2, 2026, GitHub Actions will block `pull_request_target` by default in public repositories unless an applicable Actions event policy allows it; the change applies to GitHub Free, Team, and Enterprise Cloud, not Enterprise Server, and excludes private and internal repositories. Because this trigger runs with base-repository secrets, untrusted fork code can put workflows at risk. The rule is currently in evaluate mode, and Insights can identify affected runs. Two temporary brownouts will block matching runs on November 9 and another scheduled window; blocked attempts fail with an error annotation, then enforcement returns to evaluate mode. Before the first brownout, maintain the default block or use an event policy, optionally targeting specific workflow files, to allow workflows that depend on the trigger. Enforcement was previously scheduled for November 2.

### Source excerpt

Starting December 2, 2026, GitHub Actions will block pull_request_target events by default in all public repositories, unless an applicable Actions event policy explicitly allows them. Enforcement was previously scheduled for... The post pull_request_target blocked by default December 2 appeared first on The GitHub Blog.

## Stuck on Red? Understanding GitHub Actions Failing Streaks

DevFeed: [Stuck on Red? Understanding GitHub Actions Failing Streaks](<https://devfeed.tech/articles/stuck-on-red-understanding-github-actions-failing-streaks-112683.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.41863>)

Author: Aref Talebzadeh Bardsiri (UMONS), Tom Mens (UMONS), Alexandre Decan (UMONS), Thomas Degueule (LaBRI), Jean-R\\'emy Falleri (LaBRI)

Published: 2026-11-02T05:00:00Z

Content type: news

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [failure](<https://devfeed.tech/tags/failure.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [maintainers](<https://devfeed.tech/tags/maintainers.md>), [network](<https://devfeed.tech/tags/network.md>), [repository](<https://devfeed.tech/tags/repository.md>), [service](<https://devfeed.tech/tags/service.md>), [workflow](<https://devfeed.tech/tags/workflow.md>)

### AI overview

Across 30.9 million GitHub Actions runs from 154,000+ workflows, failures commonly persist in streaks: three quarters of failing runs follow another failure, and half of workflows with at least three runs have a streak. Multi-purpose workflows have streaks more often, even at the same size. Although most streaks end within hours, the one in five lasting over a day account for most time spent failing. Repository changes do not explain every transition: a third of streaks start and two fifths end without a change; in a sample of 100, those ending without a change most often involved network problems or external services. The findings caution maintainers against attributing failures automatically to the latest commit, and suggest flagging unchanged-repository failures and alerting maintainers when a workflow remains failing for more than a day.

### Source excerpt

arXiv:2610.41863v1 Announce Type: new Abstract: GitHub Actions is the de facto CI/CD service for GitHub repositories. Its workflows should not fail when they are not expected to, nor keep on failing too long. We empirically study failing streaks, i.e., uninterrupted series of failing runs of a workflow, in 30.9M+ runs of 154K+ workflows of 43K+ GitHub repositories over 238 days. We study how failing streaks begin and end, and what happens during them, based on the trigger and the commit of each run. We also classify all workflows by their purposes, such as building, testing or deploying, and we inspect the logs of a small sample of failing streaks. Failing runs mostly come in streaks: three quarters of them follow another failing run, and half of the workflows with at least three runs have at least one failing streak. Workflows serving multiple purposes have failing streaks more often, even at the same size. Most failing streaks end within hours, but the one in five that last more than a day account for the lion's share of the time that workflows spend failing. A third of the failing streaks start, and two in five end, without any change to the repository. In a sample of 100 failing streaks, those that end this way most often fail because of network issues or an external service. These findings suggest that maintainers should not assume that a failure comes from the last commit. GitHub and tool builders could flag failures that occur without any change to the repository, and alert the active maintainers when a workflow stays failing for more than a day.

## Building a Docs-as-Code Workflow With Markdown, Mermaid, and GitHub Actions

DevFeed: [Building a Docs-as-Code Workflow With Markdown, Mermaid, and GitHub Actions](<https://devfeed.tech/articles/building-a-docs-as-code-workflow-with-markdown-mermaid-and-github-actions-106882.md>)

Original publisher: [Read original article](<https://hackernoon.com/building-a-docs-as-code-workflow-with-markdown-mermaid-and-github-actions?source=rss>)

Author: Himashi Meththasena

Published: 2026-10-29T16:49:44Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Documentation](<https://devfeed.tech/topics/documentation.md>), [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [Markdown](<https://devfeed.tech/topics/markdown.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [MkDocs](<https://devfeed.tech/topics/mkdocs.md>)

Tags: [actions](<https://devfeed.tech/tags/actions.md>), [api](<https://devfeed.tech/tags/api.md>), [api-documentation](<https://devfeed.tech/tags/api-documentation.md>), [apis](<https://devfeed.tech/tags/apis.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [automated](<https://devfeed.tech/tags/automated.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [building](<https://devfeed.tech/tags/building.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [ci-cd-pipeline](<https://devfeed.tech/tags/ci-cd-pipeline.md>), [developer-onboarding](<https://devfeed.tech/tags/developer-onboarding.md>), [docs](<https://devfeed.tech/tags/docs.md>), [docs-as-code](<https://devfeed.tech/tags/docs-as-code.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [internal-developer-portals](<https://devfeed.tech/tags/internal-developer-portals.md>), [markdown](<https://devfeed.tech/tags/markdown.md>), [mermaid](<https://devfeed.tech/tags/mermaid.md>), [mermaid-js](<https://devfeed.tech/tags/mermaid-js.md>), [mkdocs](<https://devfeed.tech/tags/mkdocs.md>), [technical-documentation](<https://devfeed.tech/tags/technical-documentation.md>), [wiki](<https://devfeed.tech/tags/wiki.md>), [workflow](<https://devfeed.tech/tags/workflow.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

The article describes replacing a detached engineering wiki with documentation maintained alongside code in each repository's `/docs` directory and updated in the same Git commits as code changes. It uses Mermaid definitions for diagrams, OpenAPI or Swagger annotations for REST APIs, and Protobuf definitions for gRPC so API references can be generated during builds. GitHub Actions checks documentation in pull requests for broken links, dead URLs, and formatting; after merges, MkDocs Material or Docusaurus can publish Markdown from multiple services to a searchable internal portal. The article reports onboarding time falling from two weeks to under three days and matching Markdown updates appearing in over 85% of architectural PRs. These are the article's reported results; it gives no measurement method.

### Source excerpt

How we replaced an outdated engineering wiki with Docs-as-Code using Markdown, Mermaid, GitHub Actions, and automated documentation workflows.

[Next page](<https://devfeed.tech/topics/github-actions.md?cursor=WyIyMDI2LTEwLTI5VDE2OjQ5OjQ0KzAwOjAwIiwgIjU3Nzk1ZDkwLWFhMzktNDA4ZC1iYzY4LWEyY2ZjNjAyMGFmYiJd>)