# CI/CD workflows Published articles for CI/CD workflows. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Turborepo and Vercel Remote Cache now support OpenID Connect (OIDC) DevFeed: [Turborepo and Vercel Remote Cache now support OpenID Connect (OIDC)]() Original publisher: [Read original article]() Author: Mery Kaftar Published: 2026-07-30T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [OpenID connect (OIDC)](), [Vercel](), [Cache](), [CI/CD](), [GitHub](), [Command-line interface]() Tags: [ci-cd](), [ci-cd-workflows](), [documentation](), [github](), [oidc](), [openid-connect](), [policy](), [remote](), [tokens](), [vercel]() ### AI overview Turborepo and Vercel Remote Cache now support exchanging OIDC tokens from CI/CD workflows for short-lived Turborepo access tokens. The article recommends migrating from long-lived Personal Access Tokens to OIDC and explains where to configure the required policy. ### Source excerpt You can now exchange OIDC tokens from CI/CD workflows, including GitHub workflows, for short-lived Turborepo access tokens. These tokens grant access to Vercel's Remote Cache, and are a more secure alternative to long-lived Personal Access Tokens (PATs). OIDC tokens are short-lived, only grant access to Vercel Remote Cache, and are associated with your Vercel team, rather than a specific team member. We recommend all customers migrate their CI/CD workflows from PATs to OIDC. Get started by adding a Turborepo OIDC policy under Settings -> Build and Deployment -> OIDC Policies for CLI Access and learn more in the documentation. Read more ## Introducing Chainguard Repository: A unified experience for secure-by-default open source artifacts DevFeed: [Introducing Chainguard Repository: A unified experience for secure-by-default open source artifacts]() Original publisher: [Read original article]() Published: 2026-03-17T00:00:00Z Content type: release Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard repository](), [chainguard](), [Open Source](), [Security](), [Containers]() Tags: [agent-skills](), [ai-agents](), [chainguard](), [chainguard-repo](), [chainguard-repository](), [ci-cd-workflows](), [container-images](), [containers](), [libraries](), [open-source](), [open-source-artifacts](), [packages](), [policy](), [secure-by-default](), [virtual-machine-images]() ### AI overview Chainguard introduces Chainguard Repository, a unified experience for consuming secure-by-default open source artifacts with configurable policy enforcement. It brings together container images, libraries, OS packages, agent skills, CI/CD workflows, and virtual machine images through Chainguard-managed endpoints and provides compliance controls, security improvements through source rebuilds, and visibility dashboards. ### Source excerpt Chainguard Repository is a single, Chainguard-managed experience for pulling secure-by-default artifacts with built-in, configurable policy enforcement. ## Introducing Chainguard Actions: CI/CD workflows you can trust DevFeed: [Introducing Chainguard Actions: CI/CD workflows you can trust]() Original publisher: [Read original article]() Published: 2026-03-17T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard actions](), [CI/CD](), [GitHub Actions](), [supply-chain-security](), [Security](), [AI-assisted coding]() Tags: [ai-coding-agents](), [chainguard](), [chainguard-actions](), [chainguard-for-github](), [ci-cd](), [ci-cd-workflows](), [coding-agents](), [github](), [github-actions](), [secure-ci-cd-workflows](), [secure-github-actions](), [security](), [software-supply-chain]() ### AI overview Chainguard introduces Chainguard Actions, a securely rebuilt and continuously maintained catalog of GitHub Actions and similar CI/CD workflows. The service aims to provide secure-by-default automation for privileged software delivery pipelines, reducing risks from unaudited third-party workflows, secret exposure, unsafe shell expressions, and insecure input handling. ### Source excerpt Chainguard Actions is a securely rebuilt catalog of GitHub Actions and similar CI/CD workflows built and continuously maintained in the Chainguard Factory. ## Watch the on-demand webinar: Shift left without the strain DevFeed: [Watch the on-demand webinar: Shift left without the strain]() Original publisher: [Read original article]() Author: Rob Samuels Published: 2025-07-14T13:00:00Z Content type: article Language: en Sources: [PortSwigger Blog]() Topics: [Application Security](), [CI/CD](), [Testing](), [Docker](), [GitHub Actions](), [GitLab](), [Jenkins](), [YAML](), [configuration]() Tags: [ci-cd](), [ci-cd-workflows](), [configuration](), [containers](), [docker](), [false-positives](), [github-actions](), [gitlab](), [jenkins](), [security](), [shift-left](), [software-delivery](), [yaml]() ### AI overview This article promotes an on-demand webinar about shifting application security left without slowing software delivery. It discusses the challenges of integrating DAST into CI/CD workflows, including slow scans, false positives, and workflow friction, and presents Burp Suite DAST as a fast, configurable, Docker-based solution that integrates with common pipeline tools. ### Source excerpt Shifting security left promises faster, safer software delivery - but for many teams, that promise is undercut by painful scan performance, false positives, and pipeline friction. In our recent webina ## CI CD for OpenHarmony Project -- GitHub Action DevFeed: [CI CD for OpenHarmony Project -- GitHub Action]() Original publisher: [Read original article]() Author: Payam Zahedi Published: 2024-12-09T12:05:48Z Content type: tutorial Language: en Sources: [Snapp Mobile - Medium]() Topics: [GitHub Actions](), [CI/CD](), [GitHub](), [Development]() Tags: [ark-ts](), [build](), [building](), [ci-cd](), [ci-cd-pipeline](), [ci-cd-workflows](), [github](), [github-action](), [github-actions](), [harmony-os](), [open-harmony](), [sdk](), [testing](), [verify]() ### AI overview This tutorial explains how to create a GitHub Actions CI/CD workflow for building and verifying an OpenHarmony application. It introduces the roles of DevEco Studio, Hvigor, OHPM, the OpenHarmony Code Linter, and the reusable oh-action for preparing the required SDK and command-line tools. ### Source excerpt CI CD for OpenHarmony Project -- GitHub Action When developing OpenHarmony, we typically use DevEco Studio to write our code, build the project, test it, and run it on our devices, with DevEco Studio taking care of everything under the hood. However, as engineers, we love to automate repetitive processes, right? This is where CI/CD workflows become incredibly useful. GitHub Actions, in particular, is a popular and highly customizable workflow solution. In this article, we'll explore how to create a workflow on GitHub Actions to build and verify our OpenHarmony application. A Little Context To write our GitHub Action workflow, we first need to understand how DevEco Studio works under the hood. Specifically, what tools does it install, and how are they used? In this article, we won't dive too deep into all OpenHarmony tools and DevEco Studio capabilities. Instead, we'll provide a brief overview to understand the components needed for our workflow. hvigorw Hvigor is a simple build tool, much like Gradle for Android, but designed specifically for OpenHarmony apps. It helps you manage tasks, dependencies, and builds easily. DevEco Studio uses hvigorw to build, test, and run apps on devices. ohpm OHPM (OpenHarmony Package Manager) is akin to npm for JavaScript, but tailored for OpenHarmony applications. It helps facilitate the publishing, installation, and management of dependencies for shared packages. DevEco Studio uses OHPM to manage third-party libraries within OpenHarmony projects. Code Linter OpenHarmony's Code Linter is a tool that checks ArkTS and TypeScript code for best practices and coding standards. It helps developers identify and fix issues during development, ensuring high-quality code. Now that we have a good understanding of the tools involved, the next step is to bring these components together into a cohesive GitHub Action that can automate our workflow. This is where oh-action steps in. GitHub - Snapp-Mobile/oh-action: The oh-action is a GitHub Action t