Notice about upcoming new format for GitHub App installation tokens - GitHub Changelog
Notice about upcoming new format for GitHub App installation tokens Starting April 27th 2026 and over the coming weeks, we will begin a staged rollout that updates the format of newly minted GitHub App installation tokens, making them more performant and improving the reliability of our API surface. If your application expects or relies on installation tokens being exactly 40 characters long, it m
GitHub - joschi/blueskyfeedbot: A bot that posts RSS feeds to Bluesky via GitHub Actions
name: FeedBot on: schedule: # This will run every five minutes. Alter it using https://crontab.guru/. - cron: '*/5 * * * *' workflow_dispatch: # This allows manually running the workflow from the GitHub actions page concurrency: group: feedbot jobs: rss-to-bluesky: runs-on: ubuntu-latest steps: - name: Generate cache key uses: actions/github-script@v6 id: generate-key with: script: | core.setOutpu
Bitwarden CLI Compromised in Ongoing Checkmarx Supply Chain ...
Socket researchers discovered that the Bitwarden CLI was compromised as part of the ongoing Checkmarx supply chain campaign. The open source password manager serves more than 10 million users and over 50,000 businesses, and ranks among among the top three password managers by enterprise adoption. The affected package version appears to be @bitwarden/cli2026.4.0, and the malicious code was publishe
GitHub - dsherret/gagen: Generate complex GitHub Actions YAML files using a declarative API.
Generate complex GitHub Actions YAML files using a declarative API. Gagen lets you define workflows in TypeScript with a fluent, declarative API that automatically resolves step ordering and propagates conditions. The condition propagation helps skip unnecessary setup steps and eliminates needing to repeat condition text over and over again. Additionally, gagen automatically pins dependencies in t
GitHub - redwoodjs/agent-ci: Agent-CI is local GitHub Actions for your agents.
Run GitHub Actions on your machine. Caching in ~0 ms. Pause on failure. Fix and retry — before you commit, before you push. Agent CI is a ground-up rewrite of the GitHub Actions orchestration layer that runs entirely on your own machine. It doesn't wrap or shim the runner: it replaces the cloud API that the official GitHub Actions Runner talks to, so the same runner binary that executes your jobs
hackerbot-claw: An AI-Powered Bot Actively Exploiting GitHub Actions - Microsoft, DataDog, and CNCF Projects Hit So Far - StepSecurity
A week-long automated attack campaign targeted CI/CD pipelines across major open source repositories, achieving remote code execution in at least 4 out of 7 targets. The attacker, an autonomous bot called hackerbot-claw, used 5 different exploitation techniques and successfully exfiltrated a GitHub token with write permissions from one of the most popular repositories on GitHub. We're entering an
Home | GitHub Agentic Workflows
Repository automation, running the coding agents you know and love, with strong guardrails in GitHub Actions. Imagine a world where improvements to your repositories are automatically delivered each morning, ready for you to review. Issues are automatically triaged, CI failures analyzed, documentation maintained and tests improved. All defined via simple markdown files. GitHub Agentic Workflows de
arm64 standard runners are now available in private repositories - GitHub Changelog
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 performance benefits of arm64 processors and run native multi-architecture builds without the overhead of virtualization or emu
Towards a secure by default GitHub Actions · community · Discussion #179107
Why are you starting this discussion? Product Feedback What GitHub Actions topic or product is this about? Workflow Configuration Discussion Details Today, GitHub announced upcoming changes to the pull_request_target event, and environment protection rules. This is one of the first steps in a broader roadmap to make GitHub Actions more secure by default and we want to use this discussion post for
Actions pull_request_target and environment branch protections changes - GitHub Changelog
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 edge cases in how these events operate on user-controlled branches that may result in unexpected exec
Pricing changes for GitHub Actions
TLDR: We’re postponing the announced billing change for self-hosted GitHub Actions to take time to re-evaluate our approach. We are continuing to reduce hosted-runners prices by up to 39% on January 1, 2026. We’ve read your posts and heard your feedback. We’re postponing the announced billing change for self-hosted GitHub Actions to take time to re-evaluate our approach. We are continuing to reduc
GitHub Actions cache size can now exceed 10 GB per repository - GitHub Changelog
Menu. Currently selected: 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 beyond the previous 10 GB per-repository cache cap using a pay-as-you-go model. All repositories will continue to receive
GitHub ActionsでESLintのShardingを実装して、CIの実行時間を51%削減しました - newmo 技術ブログ
newmoでは、pnpm workspaceで管理している複数のアプリケーションやライブラリに対してESLintを実行しています。 プロジェクトの成長とともにLint対象のファイル数が増加し、CI実行時間とメモリ使用量が増加していました。GitHub Actionsのmatrixオプションを使用した動的なShardingを実装し、これらの問題に対応しました。 newmoフロントエンドの開発原則 newmoのフロントエンド開発では、次の原則を重視しています。 1つ目は、「同じ目的を達成するための手段を統一する」という原則です。同じ目的に対する複数の手段が混在するよりも、統一した手段を使うことで学習コストや保守コストを削減できます。例えば、npmパッケージのバージョン管理では、One Version Ruleに基づき、同じ目的を持つライブラリは1つに絞っています。これは「同じコードを書かない」
New date for enforcement of cache eviction policy - GitHub Changelog
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 evict the oldest cache entries every 24 hours to keep usage below this limit. We’re changing the eviction interval to every hour. If your repositories use more than 10 GB of cache in a 24-hour period, you have received a
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
GitHub - mizchi/actrun: GitHub Actions compatible local runner
Update: Ongoing Investigation and Continued Remediation
GitHub - multimediallc/codeowners-plus: Feature-rich alternative to GitHub Code Owners for monoliths and mono-repos
GitHub - flatt-security/setup-takumi-guard-npm: GitHub Action to configure npm with Takumi Guard registry auth via OIDC
Release v6.0.0 · actions/setup-node
GitHub - danielroe/provenance-action: Fail CI when dependencies in your lockfile lose npm provenance or trusted publisher status