Use cpflow 5.1.1 release tag#763
Conversation
Greptile SummaryThis PR bumps the bundled
Confidence Score: 5/5All changes are mechanical version-string substitutions with no logic, schema, or interface changes; safe to merge. Every changed line is either a gem version pin, a workflow No files require special attention; the promote-to-production workflow is the most sensitive file touched, and its two ref fields ( Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[Gemfile / Gemfile.lock\ncpflow 5.1.0 → 5.1.1] --> B[bundle exec cpflow\nupdate-github-actions]
B --> C[6 GitHub Actions workflows\nuses: ...@d8877ca → @v5.1.1]
C --> D1[cpflow-cleanup-stale-review-apps]
C --> D2[cpflow-delete-review-app]
C --> D3[cpflow-deploy-review-app]
C --> D4[cpflow-deploy-staging]
C --> D5[cpflow-help-command]
C --> D6[cpflow-review-app-help]
C --> D7[cpflow-promote-staging-to-production\ncheckout ref + control_plane_flow_ref]
B --> E[4 doc files\nlinks main → v5.1.1\nremove canary language]
Reviews (1): Last reviewed commit: "Use cpflow 5.1.1 release tag" | Re-trigger Greptile |
WalkthroughThis PR pins the entire cpflow CI automation stack from a temporary hardening commit to the stable Changescpflow v5.1.1 Pin
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related issues
Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
🚀 Quick Review App CommandsWelcome! Here are the commands you can use in this PR:
|
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
| cpflow_version: ${{ vars.CPFLOW_VERSION }} | ||
| # The setup action validates CPFLOW_VERSION against this full workflow ref. | ||
| control_plane_flow_ref: shakacode/control-plane-flow/.github/workflows/cpflow-promote-staging-to-production.yml@d8877ca0c9c1d88947f322903e4a4344641029ba | ||
| control_plane_flow_ref: shakacode/control-plane-flow/.github/workflows/cpflow-promote-staging-to-production.yml@v5.1.1 |
There was a problem hiding this comment.
The ref: checkout (line 72) and control_plane_flow_ref here must always use the same tag — a mismatch causes the setup action's CPFLOW_VERSION validation to fail. They're correctly in sync now, but worth calling out explicitly for the next upgrade so both lines get bumped together.
Review: Use cpflow 5.1.1 release tagOverall: Clean, well-verified dependency bump — no blocking issues. What this doesUpgrades Strengths
ConsiderationsSecurity — tag mutability (low risk) Documentation link pinning Test coverage |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/cpflow-promote-staging-to-production.yml:
- Line 72: Replace mutable tag references to shakacode/control-plane-flow with
the immutable commit SHA 610dd36cb9abf14a064003c8d388b8c77c4137d7: change the
actions/checkout usage that currently has "ref: v5.1.1" to use "ref:
610dd36cb9abf14a064003c8d388b8c77c4137d7", and update the variable/setting that
contains "control_plane_flow_ref: ...@v5.1.1" to reference the same commit SHA
instead of the tag.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 3d310358-4bda-434b-a3aa-e5f65401e83d
⛔ Files ignored due to path filters (1)
Gemfile.lockis excluded by!**/*.lock
📒 Files selected for processing (12)
.controlplane/docs/testing-cpflow-github-actions.md.controlplane/readme.md.controlplane/shakacode-team.md.github/cpflow-help.md.github/workflows/cpflow-cleanup-stale-review-apps.yml.github/workflows/cpflow-delete-review-app.yml.github/workflows/cpflow-deploy-review-app.yml.github/workflows/cpflow-deploy-staging.yml.github/workflows/cpflow-help-command.yml.github/workflows/cpflow-promote-staging-to-production.yml.github/workflows/cpflow-review-app-help.ymlGemfile
|
@coderabbitai resolve |
✅ Action performedComments resolved and changes approved. |
justin808
dismissed
coderabbitai[bot]’s stale review
False positive: this PR intentionally moves generated cpflow wrappers from the unreleased commit-SHA canary to the published v5.1.1 release tag. The 5.1.1 generator emits release-tag refs as steady state; immutable SHAs remain documented for short-lived unreleased upstream tests. Validated with bin/test-cpflow-github-flow bundle exec cpflow reporting cpflow refs: v5.1.1.
✅ Review App DeletedReview app for PR #763 is deleted |
1 participant
Summary
cpflowfrom 5.1.0 to 5.1.1v5.1.1v5.1.1release tag pathVerification
bin/conductor-exec gem list -r '^cpflow$' -aconfirmed 5.1.1 is publishedgit ls-remote --tags https://github.com/shakacode/control-plane-flow.git refs/tags/v5.1.1confirmed the upstream tag existsbin/conductor-exec bundle checkbin/conductor-exec bundle exec cpflow --version->5.1.1bin/conductor-exec bundle exec cpflow update-github-actions --staging-branch masterbin/conductor-exec bin/test-cpflow-github-flow bundle exec cpflow->cpflow refs: v5.1.1bin/conductor-exec ruby -e 'require "yaml"; Dir[".github/workflows/*.yml"].sort.each { |path| YAML.load_file(path, aliases: true); puts path }'git diff --checkbin/conductor-exec bundle exec rubocop/Users/justin/.agents/skills/autoreview/scripts/autoreview --mode local-> no accepted/actionable findingsNotes
bin/conductor-exec bundle exec rspecwas attempted locally but blocked because PostgreSQL is not running on/tmp/.s.PGSQL.5432; CI should exercise the suite in its normal environment.Note
Medium Risk
Changes every cpflow-driven deploy and production promotion workflow ref; risk is limited to a published patch release but still affects CI/CD and promotion paths.
Overview
Bumps the bundled
cpflowgem from 5.1.0 to 5.1.1 and aligns all generated Control Plane GitHub Actions wrappers with upstream release tagv5.1.1, replacing the temporaryd8877ca…commit-SHA pins.Reusable workflows for review apps, staging, cleanup, and help now call
shakacode/control-plane-flow/...@v5.1.1. Production promotion checks out the same tag and passescontrol_plane_flow_refwith@v5.1.1so runtime validation stays in sync with the wrappers.Docs under
.controlplane/and.github/cpflow-help.mddescribev5.1.1as the steady-state pin (promotion hardening and release-runner timeout fixes) and refresh the update loop to usebundle update cpflowandbundle exec cpflow update-github-actionsinstead of ad-hoc upstream checkout paths.Reviewed by Cursor Bugbot for commit e03f7bc. Bugbot is set up for automated code reviews on this repo. Configure here.
Summary by CodeRabbit