Repository navigation
CI: Add RELEASE.md for trunklet-format release specifics - #1
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the
 |
jnasbyupgrade
changed the title
faedea7 to
e6f9ee4
Compare
| - **No release has a tag yet.** `0.1`, `0.1.0`, `0.1.1` and `0.2.0` exist as branches on upstream. Where shared step 1 compares against the previous release's tag, use the `0.2.0` branch (or PGXN.org). | ||
| - **Never create a tag named like one of those branches.** The ref becomes ambiguous and `git push origin <version>` fails with `src refspec <version> matches more than one`. | ||
| - **Both `default_version` and `META.in.json` are `stable` on master.** `make post-tag-version-bump` resets only the control file; set the `version` fields in `META.in.json` back to `stable` by hand in the same commit (shared step 8). | ||
| - **The update script is `sql/trunklet-format--0.2.0--stable.sql`.** At release, `git mv` it to `sql/trunklet-format--0.2.0--<new-version>.sql`, then re-seed `sql/trunklet-format--<new-version>--stable.sql`. |
There was a problem hiding this comment.
Uhm... why do we need to mention this? What's different here than standard process?
There was a problem hiding this comment.
Claude here: nothing — the shared process already covers the git mv and re-seed of the --stable update script, and the filename follows from its sql/<ext>--<last-released-version>--stable.sql pattern. Removed the bullet in f6dea07.
| - **Never create a tag named like one of those branches.** The ref becomes ambiguous and `git push origin <version>` fails with `src refspec <version> matches more than one`. | ||
| - **Both `default_version` and `META.in.json` are `stable` on master.** `make post-tag-version-bump` resets only the control file; set the `version` fields in `META.in.json` back to `stable` by hand in the same commit (shared step 8). | ||
| - **The update script is `sql/trunklet-format--0.2.0--stable.sql`.** At release, `git mv` it to `sql/trunklet-format--0.2.0--<new-version>.sql`, then re-seed `sql/trunklet-format--<new-version>--stable.sql`. | ||
| - **Before releasing, recheck the trunklet 0.2.0 wording in `HISTORY.asc` and `README.md`.** It says trunklet 0.2.0 has no update path and must be dropped and recreated; that stops being true once a trunklet release containing its `0.2.0--0.2.1` update script is on PGXN. |
There was a problem hiding this comment.
I'm going to release a corrected trunklet at the same time as trunklet-format. I believe that means this item can just go.
There was a problem hiding this comment.
Claude here: removed that bullet in the amended commit (d2c61aa).
e6f9ee4 to
d2c61aa
Compare
d2c61aa to
f6dea07
Compare
Adds
RELEASE.mdlinking the shared release process plus the trunklet-format-specific points: releases0.1,0.1.0,0.1.1and0.2.0are branches, not tags (so don't create a same-named tag); and master sits onstablein both the control file andMETA.in.json.Rebased onto current master (vendored pgxntool 2.4.0,
stableadopted);RELEASE.mdis the only file changed.