Pipery actions v1.1.0#

v1.1.0 is the current release for the supported Pipery action catalog.

Use exact v1.1.0 tags when you want reproducible workflows:

- uses: pipery-dev/golang-ci@v1.1.0

GitLab and Bitbucket examples use the same release tag:

include:
  - project: pipery-dev/golang-ci
    ref: v1.1.0
    file: /.gitlab-ci.yml

definitions:
  imports:
    pipery-golang-ci: pipery-dev/golang-ci:v1.1.0

What Changed#

Area	Update
Versioning	Public docs and examples now point at `v1.1.0` for exact pinning.
Cross-platform builds	Go and C/C++ CI support release targets such as `linux/amd64`, `linux/arm64`, `windows/amd64`, and `darwin/amd64`.
Action validation	Pipery action repositories keep scenario test projects for happy paths and failure paths before release.
ArgoCD CD	`pipery-argocd-cd` can validate Helm charts with dependency update, lint, and template rendering.
GitOps values	`pipery-argocd-cd` supports `deploy_values_path` for adding a deployment values file to the generated ArgoCD update.
Runtime secrets	Helm charts keep sensitive runtime values in Kubernetes secrets while non-sensitive deployment configuration stays in values files.

Current Action Set#

CI actions:

pipery-cpp-ci@v1.1.0
pipery-docker-ci@v1.1.0
pipery-golang-ci@v1.1.0
pipery-java-ci@v1.1.0
pipery-npm-ci@v1.1.0
pipery-python-ci@v1.1.0
pipery-rust-ci@v1.1.0
pipery-terraform-ci@v1.1.0

CD actions:

pipery-ansible-cd@v1.1.0
pipery-argocd-cd@v1.1.0
pipery-cloudrun-cd@v1.1.0
pipery-docker-cd@v1.1.0
pipery-helm-cd@v1.1.0
pipery-terraform-cd@v1.1.0

Upgrade Notes#

Pinned v1 usage still follows the major release line. Switch to v1.1.0 when you want a locked rollout for regulated repositories, golden workflow templates, or platform-team managed examples.

For ArgoCD chart publishing, prefer:

- uses: pipery-dev/argocd-cd@v1.1.0
  with:
    publish_helm_chart_update: true
    validate_helm_chart: true
    chart_path: charts/my-app
    deploy_values_path: deploy/values.yaml

Keep tokens and OAuth client secrets in Kubernetes secrets or CI secrets. Use Helm values for non-sensitive settings such as hostnames, namespaces, chart paths, image repositories, and redirect URLs.