Skip to content

CI: Add RELEASE.md for trunklet-format release specifics #1

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

Draft
jnasbyupgrade wants to merge 2 commits into
base: master
Choose a base branch
from
Draft

CI: Add RELEASE.md for trunklet-format release specifics #1

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c0c4ed6
Add RELEASE.md: this repo's pgxntool vendors branch-based tag/dist
jnasbyupgrade Aug 10, 2026
faedea7
Rewrite RELEASE.md as a minimal local-deviation note
jnasbyupgrade Oct 25, 2026
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
9 changes: 9 additions & 0 deletions RELEASE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
# RELEASE.md

This repo follows the shared release process in [`../ai/RELEASE.md`](https://github.com/Postgres-Extensions/ai/blob/main/RELEASE.md), with one local deviation.

Releases `0.1`, `0.1.0`, `0.1.1` and `0.2.0` exist as branches on upstream, not tags. `make tag` creates a real tag for each release from here on.

Where the shared doc compares against the previous release's tag, use the `0.2.0` branch (or PGXN.org, per step 1 of the shared doc).

Never create a tag whose name matches one of those branches: the ref becomes ambiguous and `git push origin <version>` fails with `src refspec <version> matches more than one`.