[jnasbyupgrade]

Version bump to 0.2.0 per the shared release process.

• default_version, META.in.json (and regenerated META.json) set to 0.2.0
• sql/object_reference--0.1.0--stable.sql renamed to --0.1.0--0.2.0.sql; generated sql/object_reference--0.2.0.sql committed
• New HISTORY.asc with the 0.2.0 changes
• CLAUDE.md links the shared release process

After merge: make tag / make dist, upload to PGXN, then reset default_version to stable and re-seed sql/object_reference--0.2.0--stable.sql.

[coderabbitai]

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

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 329c8f0d-1e4d-4cd7-b8f3-44be76c6826a

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

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

• X
• Mastodon
• Reddit
• LinkedIn

[github-actions]

Claude finished @jnasbyupgrade's task in 15s —— View job

---

Code review: PR #47 (Release 0.2.0)

No blocking issues found.

I checked the version bumps, the upgrade-script rename, HISTORY.asc and the CLAUDE.md link.

• default_version, META.in.json and META.json all say 0.2.0 and agree with each other.
• sql/object_reference--0.1.0--stable.sql was renamed to --0.1.0--0.2.0.sql with no content change (100% rename). The new sql/object_reference--0.2.0.sql sits next to it.
• HISTORY.asc follows the usual format. The count_nulls claim is consistent with requires = 'cat_tools' in the control file.

I did not build the extension or run the tests. I also did not compare the generated object_reference--0.2.0.sql against sql/object_reference.sql. The /code-review skill failed to run, so I reviewed the diff by hand. Rebuilding with make and confirming the generated file is unchanged would cover that gap.

The post-merge steps in the PR description (make tag / make dist, PGXN upload, reset to stable) are not part of this PR.

[jnasbyupgrade]

Reads too much like directions on how to update, obscuring the backwards compatability break.

[jnasbyupgrade]

We now demand cat_tools 0.3.0, correct? Do we have code that checks that and provides a good error? Does META / control file specify >= 0.3.0? If not open a PR that does both.

[jnasbyupgrade]

Oh, and this item needs to be reworded. We don't "support" 0.3.0, we demand it. That should be at the top of the list, along with backwards incompatabilities. Open a PR against ../ai/ that the history for a version must list any backwards incompatabilities or special steps needed to update at the top of what changed in a version.

[github-actions]

Claude finished @jnasbyupgrade's task in 16s —— View job

---

Code review: PR #47 (Release 0.2.0)

One issue to fix. HISTORY.asc says "Any older cat_tools is rejected at CREATE EXTENSION and ALTER EXTENSION UPDATE", but nothing enforces that:

• object_reference.control has requires = 'cat_tools' with no version. Control-file requires can't express a minimum version anyway.
• META.in.json and META.json have "cat_tools": 0 under runtime prereqs. They should say 0.3.0.
• No SQL checks the installed cat_tools version. The only cat_tools check in sql/object_reference.sql is the schema check, and it's commented out as excluded code. I found no 0.3.0 or extversion check in sql/.

As written, the release note would be false. This matches @jnasbyupgrade's review request: set the META minimum to 0.3.0 and add a version check that raises a clear error. The check needs to go in both sql/object_reference.sql (so it lands in object_reference--0.2.0.sql) and sql/object_reference--0.1.0--0.2.0.sql. Per that comment it belongs in a separate PR, so I haven't changed it here.

Already addressed: the earlier HISTORY.asc feedback is handled by commit 5268063. Backwards-incompatible changes and the special update step now come first, and the "Support cat_tools 0.3.0" item is reworded as a requirement.

Not done:

• The /code-review skill failed to run, so I reviewed by hand.
• I didn't build or test.
• I didn't diff the generated object_reference--0.2.0.sql against sql/object_reference.sql.
• I didn't open the follow-up PR against ../ai/ that the review asks for.

[github-actions]

Claude finished @jnasbyupgrade's task in 13s —— View job

---

Code review: PR #47 (Release 0.2.0)

No blocking issues found. The earlier concerns are resolved.

• cat_tools minimum: META.in.json and META.json now require cat_tools 0.3.0. The version check with a clear error (object_reference requires cat_tools 0.3.0 or later) is in sql/object_reference.sql, sql/object_reference--0.1.0--0.2.0.sql and the generated sql/object_reference--0.2.0.sql. So the HISTORY.asc claim that older cat_tools is rejected at CREATE EXTENSION and ALTER EXTENSION UPDATE is now true.
• HISTORY.asc: It now opens with the backwards-incompatible changes (cat_tools 0.3.0 requirement, removed reg* columns) and the special update step. Those come before the feature list, which addresses the review feedback.
• Version bump: default_version, META.in.json and META.json agree on 0.2.0. The upgrade script is a pure rename with no content change.

Not done:

• The /code-review skill failed to run, so I reviewed by hand.
• I didn't build or run the tests.
• I didn't diff the generated object_reference--0.2.0.sql against sql/object_reference.sql.
• The ../ai/ PR about listing backwards-incompatible changes in HISTORY is outside this repo, and I didn't open it.
• The working tree has an uncommitted change to CLAUDE.md that predates this review. I left it alone.