Skip to content

Add trunklet-specific RELEASE.md #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

Open
jnasbyupgrade wants to merge 2 commits into
base: master
Choose a base branch
from
+9 −0
Open

Add trunklet-specific RELEASE.md #1

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7c64900
Add trunklet-specific RELEASE.md
jnasbyupgrade Oct 26, 2026
fb6e5fe
Cover the 0.3.3 install script in RELEASE.md and drop a redundant sen…
jnasbyupgrade Oct 26, 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 (trunklet-specific notes)

Follow [`../ai/RELEASE.md`](https://github.com/Postgres-Extensions/ai/blob/main/RELEASE.md).

## Step 1: releases 0.0.1 through 0.3.3 are branches, not tags

Each of those releases is a branch on `origin` named exactly the version; the repo has no tags before the first `make tag` release. Where step 1 says to compare against the tag, compare against that version's branch tip instead.

`sql/trunklet--0.2.0.sql`, `sql/trunklet--0.2.1.sql` and `sql/trunklet--0.3.3.sql` were committed after those versions shipped, so step 1 will flag their late last-touch dates. That is the backfill exception it describes, not drift. Each matches `sql/trunklet.sql` on its version branch, except that the 0.3.3 copy adds pgxntool's `/* DO NOT EDIT - AUTO-GENERATED FILE */` header line.
Loading