Skip to content

RELEASE.md: drop the tag-named-like-branch bullet #11

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jnasbyupgrade merged 1 commit into from
Oct 29, 2026
Merged

RELEASE.md: drop the tag-named-like-branch bullet #11

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion RELEASE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,5 +3,4 @@
This repo follows the shared release process in [`../ai/RELEASE.md`](https://github.com/Postgres-Extensions/ai/blob/main/RELEASE.md) (`make tag`, `make dist` and `make post-tag-version-bump` come from the vendored pgxntool 2.4.0). Local specifics only:

- **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).
Loading