Skip to content

chore(claude): add version-alignment + downstream-pipeline checks to release skill#85

Draft
amogiska wants to merge 1 commit intomainfrom
amogiska/release-skill-version-alignment-checks
Draft

chore(claude): add version-alignment + downstream-pipeline checks to release skill#85
amogiska wants to merge 1 commit intomainfrom
amogiska/release-skill-version-alignment-checks

Conversation

@amogiska
Copy link
Copy Markdown
Contributor

@amogiska amogiska commented May 5, 2026

Summary

  • Add a step to verify pg_stat_ch.control's default_version equals the new tag's MAJOR.MINOR before tagging (Theory's policy from Change version format, add PGXN release workflow #33). Patch and minor/major bumps get bump-specific remediation guidance — the v0.3.7 cut surfaced that the skill was happily tagging across this misalignment for months.
  • Add a step to verify sql/pg_stat_ch--<ext>.sql exists, and if default_version was bumped relative to the prior tag, that sql/pg_stat_ch--<prev>--<ext>.sql exists too. Refs chore(meta): align extension version with distribution (0.3) #84 as the precedent for the conditional-DDL migration pattern.
  • After tagging, remind the operator of the downstream handoffs (pgext-packaging auto-bump or manual update-pg-stat-ch.yml dispatch → AMI build via postgres-vm-images/trigger-build.yml → fleet rollout via clickgres-platform/clickgres-pg-amis-latest.yml).
  • Update the skill description so the new pre-flight checks show up in the available-skills index.

…release skill

When cutting v0.3.7 we discovered the extension's default_version had
been pinned at 0.1 across the entire 0.3.x distribution series, which
violated Theory's policy that the extension version should track the
distribution major.minor. The release skill happily created tags
without catching this. Update the skill to:

- Verify pg_stat_ch.control's default_version equals the new tag's
  major.minor, with bump-type-specific guidance on what to do if not.
- Verify the canonical sql/pg_stat_ch--<ext>.sql exists and, if
  default_version was bumped this release, that the
  pg_stat_ch--<prev>--<ext>.sql migration script is in place too
  (refs PR #84 as the precedent for the conditional-DDL migration).
- After tagging, remind the operator of the downstream handoffs:
  pgext-packaging auto-bump (or manual update-pg-stat-ch.yml dispatch),
  AMI build via postgres-vm-images/trigger-build.yml, AMI ID rollout
  via clickgres-platform/clickgres-pg-amis-latest.yml.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant