Skip to content

Pin cat_tools to the 0.3.0 tag now that it exists - #25

Open
jnasbyupgrade wants to merge 1 commit into
Postgres-Extensions:fix-cat-tools-installfrom
jnasbyupgrade:pin-cat-tools-0.3.0-tag
Open

Pin cat_tools to the 0.3.0 tag now that it exists#25
jnasbyupgrade wants to merge 1 commit into
Postgres-Extensions:fix-cat-tools-installfrom
jnasbyupgrade:pin-cat-tools-0.3.0-tag

Conversation

@jnasbyupgrade

Copy link
Copy Markdown
Contributor

Summary

Small follow-up to #10. cat_tools 0.3.0 has just been tagged on GitHub
(Postgres-Extensions/cat_tools) — before this, fix-cat-tools-install's
CAT_TOOLS_GIT_REF had already moved past its original raw-SHA pin to
tracking master directly (see baf0a6e), since 0.3.0 hadn't been tagged
yet and there was nothing more stable to point at.

Now that a real tag exists, this re-points CAT_TOOLS_GIT_REF at 0.3.0
instead of the moving master branch. Checked first: the 0.3.0 tag's
commit (5fa8083d...) is identical to cat_tools' current master tip, so
this is a pure reference-stability change — same commit, just a fixed,
intentional name instead of a moving branch pointer — not a behavior
change. No regression check across a range was needed since there's no
delta between the two refs.

This does NOT unblock cutting a real extension_drop PGXN release.
cat_tools 0.3.0 is tagged on GitHub but still not published to PGXN
Manager, and RELEASE.md's rule is that a dependency pinned to a git
source (rather than genuinely pgxn install-able) blocks a release. The
original fix's exit condition — revert to a plain
pgxn install 'cat_tools>=0.3.0' --sudo once it's actually on PGXN — still
stands and hasn't been reached.

What changed

  • Makefile: CAT_TOOLS_GIT_REF changed from master to 0.3.0, comment
    updated to describe the tag now existing and reiterate the
    does-not-unblock-release caveat.

Test plan

  • Ran make cat_tools from a clean state (removed the installed
    cat_tools.control/sql files first) — clone + git checkout 0.3.0 +
    install succeeded.
  • Confirmed default_version in the installed cat_tools.control
    resolves to 0.3.0, same as before.
  • make install and make test: schema and simple pass. zzz_build
    fails, but that's pre-existing and unrelated — test/expected/zzz_build.out
    hasn't changed since the initial commit, and the diff is PG17 emitting
    new %TYPE-reference NOTICE messages in extension_drop.sql itself,
    nothing to do with cat_tools or this change.

🤖 Generated with Claude Code

cat_tools 0.3.0 was just tagged on GitHub (Postgres-Extensions/cat_tools),
where before there was only a floating master branch to track (0.3.0
hadn't been tagged yet when the git-source install was added). The tag's
commit is identical to the master tip this was already tracking, so this
is a pure reference-stability improvement, not a behavior change: point
CAT_TOOLS_GIT_REF at the tag instead of the moving master branch.

This still does not unblock cutting a real extension_drop PGXN release --
cat_tools 0.3.0 is tagged on GitHub but still not published to PGXN, and
RELEASE.md requires the real thing for that. The exit condition from the
original fix (pgxn install 'cat_tools>=0.3.0' once it's actually on PGXN)
still stands.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Aug 4, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 5a609a11-aee0-4eb4-9923-833c4f59a227

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant