Repository navigation
Add trunklet-specific RELEASE.md - #1
Draft
jnasbyupgrade wants to merge 2 commits into
Draft
jnasbyupgrade wants to merge 2 commits into
jnasbyupgrade wants to merge 2 commits into
Conversation
…results This repo vendors a much older, subtree-vendored pgxntool whose make tag creates a git branch (not a tag) and predates the stable pseudo-version and verify-results mechanisms the org's shared ../ai/RELEASE.md assumes. Following that doc verbatim here would be actively wrong, so document the concrete deviations locally and point to the shared doc for everything else.
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the
 |
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
jnasbyupgrade
changed the title
jnasbyupgrade
force-pushed
the
master
branch
4 times, most recently
from
October 26, 2026 21:20
cf25b79 to
55eac10
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a trunklet-specific
RELEASE.mdthat lists only this repo's deviations from the shared release process and links to../ai/RELEASE.mdfor everything else.Releases 0.0.1 through 0.3.3 exist as branches on
originwith no git tags, whilemake tagnow creates real tags, so future releases are tags and the history has both conventions. The doc says to compare against the version branch for shared step 1, and warns against creating a tag named after an existing version branch (git treats the name as ambiguous, andmake tagfails with "exists but points to different commit").The doc also records that the
stablepseudo-version is not adopted yet (default_versionis0.3.3,HISTORY.aschas noSTABLEsection, no--stable.sqlupdate script), so the shared doc's between-releasestablesteps and step 8 do not apply until it is. The PR that adoptsstableshould delete that section.