skills.rest
lc0rp
lc0rpCOMMUNITY
Explore all skills by this author →
Website𝕏@lukekyohereGitHub

gcp-cloud-run-release-debug

Diagnose and repair GitHub Actions release pipelines deploying to GCP Cloud Run.

Updated Aug 27, 2026
Search Tags:#authentication#gcp#cloud#iam#github-actions#ci-cd#cloud-run
One-click install
npx skills add https://github.com/lc0rp/luke-agent-scripts --skill gcp-cloud-run-release-debug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gcp-cloud-run-release-debug
Source: https://github.com/lc0rp/luke-agent-scripts/tree/main/skills/gcp-cloud-run-release-debug
Command: npx skills add https://github.com/lc0rp/luke-agent-scripts --skill gcp-cloud-run-release-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose and repair GitHub Actions release pipelines that deploy to GCP Cloud Run, especially when release workflows fail in the deploy step or when IAM/auth or build paths are unclear.

Core Features & Use Cases

  • Audit release and deploy workflows to locate failure points between semantic-release, image build, and deployment.
  • Verify deploy identity and credentials (credentials_json vs workload identity) and reproduce failing cloud commands locally.
  • Patch the release flow to switch between build backends or adjust permissions with minimal disruption.

Quick Start

Use this skill to diagnose a failing Cloud Run release by running through the guided checks and selecting the smallest, correct fix (IAM, secret rotation, or workflow change).

Frequently Asked Questions about gcp-cloud-run-release-debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug a failing Cloud Run deployment in GitHub Actions?▼

Verify Cloud Run deploy identity by checking whether your GitHub Actions workflow uses credentials_json or workload identity federation, then reproduce failing gcloud commands locally to confirm permissions before patching the pipeline.

Why does my semantic-release pipeline fail when deploying to GCP Cloud Run?▼

Semantic-release pipelines fail during Cloud Run deployment due to misconfigured IAM permissions, invalid GCP_CREDENTIALS secrets, or incorrect Artifact Registry paths, requiring guided checks to isolate and repair the specific auth or build failure.

Can I use Workload Identity instead of GCP_CREDENTIALS for Cloud Run deploys?▼

You can switch from GCP_CREDENTIALS to Workload Identity by patching the release flow with minimal changes to the google-github-actions/auth configuration, verifying deploy identity, and confirming the updated permissions work locally.

What's the best way to reproduce a failing gcloud run deploy command locally?▼

Reproduce failing gcloud run deploy commands locally by extracting the exact deployment script from your GitHub Actions workflow, authenticating with the same deploy identity, and running the command against your Artifact Registry and Cloud Run target.

How do I fix Cloud Run release pipeline failures without disrupting existing workflows?▼

Fix Cloud Run release pipeline failures by applying the smallest correct patch: rotate Secret Manager values, adjust IAM roles, or switch build backends, ensuring minimal disruption to your existing semantic-release and deployment flow.

Related Skills

Explore More Software Engineering Skills→
Mrjoel97Mrjoel97
1

google-cloud-run-ops

Deploy and operate Google Cloud Run services via repository-driven workflows and Cloud Build CI/CD.

Community
Advanced
kubonykubony
10

gcp-cloudrun

Deploy, scale, and manage Cloud Run services using the gcloud CLI.

Community
Advanced
jonnymuirjonnymuir
1

ci-validation-gates

Validate CI/CD pipelines for semantic versioning, token security, and registry retry logic.

Community
Advanced
hainamchunghainamchung
54

cloud-devops

Automate multi-cloud infrastructure provisioning and DevOps workflows across AWS, Azure, and GCP.

Community
Advanced