CuraDevOps

tag: Github-Actions · 17 items

2026-09-02 · GitHub Changelog · source ↗ #github-actions#developer-experience#ai
  • Platform/SRE — Skip
  • CI/CD — Learn: Copilot can now be authorized to formally approve PRs, which could change how teams gate merges; worth evaluating if the org uses GitHub and wants to automate lightweight review sign-off.
  • Leader — Learn: AI-assisted PR approval is a governance and standards question — assess whether org policy should permit or restrict automated approvals before teams opt in independently.
2026-08-28 · GitHub Changelog · source ↗ #github-actions#workflow-retention#ci-cd
  • Platform/SRE — Skip
  • CI/CD — Plan: Starting October 1, 2026, GitHub Actions retention settings will also govern checks, workflow runs, and commit statuses — review your current retention configuration to ensure historical build data and compliance audit trails are preserved as expected before the change takes effect.
  • Leader — Skip
2026-08-22 · Docker Blog · source ↗ #github-actions#ai-agents#docker
  • Platform/SRE — Skip
  • CI/CD — Learn: Demonstrates a pattern for running isolated AI agents inside GitHub Actions using Docker Sandboxes; worth evaluating as an emerging CI workflow design, but no concrete migration or deadline exists.
  • Leader — Skip
2026-08-21 · GitHub Changelog · source ↗ #github-actions#ci-runners#windows-arm64
  • Platform/SRE — Skip
  • CI/CD — Plan: The Windows 11 arm64 VS2026 runner image is now GA on GitHub-hosted runners; teams building Windows arm64 artifacts should evaluate updating workflow runs-on labels to adopt the new image this quarter.
  • Leader — Skip
  • Signals: GA announcement
2026-08-21 · GitHub Changelog · source ↗ #github-actions#codeql#code-quality
  • Platform/SRE — Skip
  • CI/CD — Plan: If you use CodeQL in GitHub Actions, evaluate adopting the new dedicated workflow path to improve run-history clarity and accurate usage reporting — no deadline, but worth scheduling as routine pipeline hygiene.
  • Leader — Skip
  • Signals: GA announcement
2026-08-06 · GitHub Changelog · source ↗ #github-actions#code-scanning#supply-chain
  • Platform/SRE — Skip
  • CI/CD — Plan: If your org uses GitHub code scanning default setup, evaluate adopting the new github-codeql-config-file repository property to standardize CodeQL scan behavior across repos without per-repo overrides.
  • Leader — Plan: This enables centralized enforcement of code scanning standards across the org’s repositories — worth incorporating into the golden path or security policy for teams already on GitHub Advanced Security.
  • Platform/SRE — Skip
  • CI/CD — Learn: GitHub now offers AI-generated coverage workflow setup from repository Code Quality settings, reducing onboarding friction; worth evaluating if teams struggle to bootstrap coverage, but no pipeline migration is required.
  • Leader — Skip
2026-07-29 · GitHub Changelog · source ↗ #github-actions#supply-chain#security
  • Platform/SRE — Skip
  • CI/CD — Plan: GitHub now holds potentially malicious workflow runs for review in public repositories; audit your org’s Actions approval settings and ensure maintainers understand how to review held runs before merging external contributions.
  • Leader — Learn: GitHub’s new default protection against credential-stealing workflow attacks reduces supply-chain risk for orgs using public repos; worth noting as a positive vendor-risk signal when assessing GitHub Actions dependency.
2026-07-29 · GitHub Changelog · source ↗ #static-analysis#security#github-actions
  • Platform/SRE — Skip
  • CI/CD — Learn: CodeQL 2.26.1 brings improved framework coverage for Go and better analysis accuracy; worth noting if you run GitHub code scanning in pipelines, but this is a patch-level quality improvement with no breaking changes or deadline.
  • Leader — Skip
2026-07-28 · GitHub Changelog · source ↗ #github-actions#supply-chain#security
  • Platform/SRE — Skip
  • CI/CD — Plan: GitHub now holds unproven workflows pending approval on public repos — review your repository settings and approval workflows to ensure this protection is enabled and fits your release process.
  • Leader — Learn: A new GitHub platform-level control targeting supply chain attacks via compromised credentials; worth noting as a defense-in-depth signal for orgs that rely on GitHub Actions for public repositories.
  • Platform/SRE — Skip
  • CI/CD — Learn: This adds a mobile-first workflow for diagnosing and fixing failed Actions checks via Copilot agent; no pipeline changes required, but worth tracking as an AI-assisted DevEx pattern for CI triage.
  • Leader — Skip
2026-07-21 · HN (terraform) · source ↗ #github-actions#terraform#aws
  • Platform/SRE — Learn: A community module for self-hosted GitHub Actions runner autoscaling on AWS; worth evaluating if teams are self-hosting runners, but no deadline or GA milestone signals a required change.
  • CI/CD — Plan: If cost or throughput is a pain point with GitHub-hosted runners, this Terraform module offers a path to autoscaled self-hosted runners on AWS — worth scheduling an evaluation this quarter.
  • Leader — Skip
2026-07-20 · Releases: pulumi · source ↗ #pulumi#github-actions#iac
  • Platform/SRE — Plan: If your pipelines use pulumi/actions or pulumi/action-install-pulumi-cli, both have major version bumps (v6→v7, v1→v2) that likely include breaking changes; audit your workflow files and update action refs this quarter.
  • CI/CD — Plan: pulumi/actions jumped v6→v7 and pulumi/action-install-pulumi-cli jumped v1→v2 — major bumps that may break existing pipeline steps; review release notes for both actions and update workflow references before Renovate auto-merges cause unexpected failures.
  • Leader — Skip
2026-07-17 · GitHub Changelog · source ↗ #github-actions#macos#xcode
  • Platform/SRE — Skip
  • CI/CD — Learn: Public preview of the Xcode 27 macOS runner is available for early testing; pre-GA status caps this at Learn — evaluate in a non-production pipeline before GA.
  • Leader — Skip
  • Signals: pre-GA (alpha/beta/RC/preview)
2026-07-15 · GitHub Changelog · source ↗ #github-actions#security#code-scanning
  • Platform/SRE — Skip
  • CI/CD — Plan: GitHub’s AI-powered security detections now surface on PRs for languages CodeQL doesn’t cover — worth enabling to broaden supply-chain and vulnerability coverage in existing GitHub Actions workflows.
  • Leader — Learn: Expanded AI security coverage on PRs broadens GitHub’s appeal as a unified code-security platform, relevant if evaluating whether GitHub Advanced Security covers the org’s language portfolio.
2026-07-15 · GitHub Changelog · source ↗ #dependabot#supply-chain#github-actions
  • Platform/SRE — Skip
  • CI/CD — Learn: Dependabot’s new default 3-day cooldown before raising version-update PRs reduces noise from yanked or quickly-patched releases; no pipeline changes required, but worth understanding if teams rely on same-day dependency PRs.
  • Leader — Skip
2026-07-11 · GitHub Changelog · source ↗ #static-analysis#security#github-actions
  • Platform/SRE — Skip
  • CI/CD — Plan: If pipelines run CodeQL scanning on Kotlin 2.4.0 codebases, upgrade to CodeQL 2.26.0 this quarter to maintain scan coverage; the new AI prompt injection queries are worth enabling if building LLM-integrated apps.
  • Leader — Skip