You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(ci): remove jq version rewrite, add META.json check to release skill (#52)
The pgxn-tools container doesn't have jq. Instead, META.json will be
bumped manually before tagging (matching pg_clickhouse convention).
Updated the create-new-release skill to verify META.json version
matches the new tag before pushing.
Copy file name to clipboardExpand all lines: .claude/skills/create-new-release/SKILL.md
+6-3Lines changed: 6 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,20 +26,23 @@ Create and push a new semantic version release tag.
26
26
-**minor**: `v1.2.3` → `v1.3.0`
27
27
-**major**: `v1.2.3` → `v2.0.0`
28
28
29
-
5.**Validate current commit exists on remote**:
29
+
5.**Verify META.json version matches the new tag**:
30
+
Read `META.json` and check that both `version` and `provides.pg_stat_ch.version` match the new version (without the `v` prefix). If they don't match, abort and tell the user to update `META.json` first — PGXN uses this file for the release version.
31
+
32
+
6.**Validate current commit exists on remote**:
30
33
```bash
31
34
git fetch origin
32
35
git branch -r --contains HEAD
33
36
```
34
37
If no remote branch contains HEAD, abort with an error asking the user to push their commits first.
35
38
36
-
6.**Create and push the tag**:
39
+
7.**Create and push the tag**:
37
40
```bash
38
41
git tag -a <new_version> -m "Release <new_version>"
0 commit comments