Pipery Guides

Every pipery-*-ci and pipery-*-cd action runs its src/step-*.sh scripts through psh instead of plain bash:

#!/usr/bin/env psh
set -euo pipefail

ruff check .
printf …

Pipery actions v1.1.0 is the current release across the supported action catalog. The release is mostly about making the platform easier to trust: examples now use exact pins, action repositories carry richer scenario coverage, and the deployment handoff …

Some deploys need a release window but should not become a recurring scheduled workflow. That is the shape pipery-deploy-bot is built for.

A workflow can ask the bot to dispatch another GitHub Actions workflow at a specific time. The bot stores the …

Pipery Auth is now Dex-backed. Dex gives Pipery one OIDC issuer for the services that need shared identity:

https://auth.pipery.dev/dex

That issuer can broker login through GitHub, GitLab, and Bitbucket Cloud connectors, while each Pipery app keeps a clear …

Pipery has been growing from reusable GitHub Actions into a portable CI/CD layer that can run across GitHub Actions, GitLab CI, and Bitbucket Pipelines. The newer platform work is meant to make provider changes less dramatic: the pipeline family stays …

Bitbucket Pipelines is now a first-class Pipery target. Pipery repositories in the pipery-dev Bitbucket workspace, such as https://bitbucket.org/pipery-dev/npm-ci/ or https://bitbucket.org/pipery-dev/cloudrun-cd/, can expose shared pipeline definitions. …

Pipery is no longer a GitHub-only starting point. The Pipery pipeline repositories are mirrored to GitLab, so GitLab projects can import templates from gitlab.com/pipery-dev and keep the pipeline source close to the CI system that runs it.

That matters for …

Once a service is built and tested, the next question is how to deploy it without turning your workflow into another custom shell project. pipery-dev/cloudrun-cd gives you a reusable Cloud Run deployment step with the same observability story as the CI …

Container pipelines get messy quickly. pipery-dev/docker-ci wraps the usual Docker CI sequence into one reusable action, with structured logging built in.

Instead of hand-writing Docker login, build, scan, test, tag, and push steps in every repository, you …

If your Node.js workflow keeps growing one shell step at a time, pipery-dev/npm-ci is a clean place to stop and standardize it.

This action is a complete CI workflow for npm and Yarn projects. It covers SAST, dependency scanning, linting, build, test, …