Repository navigation
Release 1.1.0 - #66
Conversation
The only change since 1.0.0 that reaches users is that the extension no longer requires superuser to install. That lives in the control file, not in any SQL, so the extension version stays at 1.0.0 and only the distribution version moves. default_version is pinned to 1.0.0 for the tag; it returns to `stable` right after. A root .gitattributes keeps the `--stable` scripts out of the release archive.
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the
|
|
Claude finished @jnasbyupgrade's task in 10s —— View job Code review: no issues found
I didn't build or run the tests. The review is based on the diff and the repo files. The follow-up PR needs to restore |
The release commit carries no *--stable* files; the return-to-stable PR after the tag re-seeds them. export-ignore is no longer needed.
|
Claude finished @jnasbyupgrade's task in 10s —— View job Code review: no blocking issues
Two notes, neither blocking:
I didn't build or run the tests. |
|
Claude finished @jnasbyupgrade's task in 11s —— View job Code review: no issues found
The follow-up PR after I didn't build or run the tests. The review is based on the diff and the repo files. |
Cut distribution 1.1.0; the extension version stays at 1.0.0. The only user-facing change since 1.0.0 is that the extension no longer requires superuser to install. That lives in the control file, not in any SQL, so there is no update script to ship and nothing for
ALTER EXTENSION ... UPDATEto do.default_versionis pinned to1.0.0for the tag. The release carries no--stablescripts:sql/count_nulls--stable.sql(generated install script) andsql/count_nulls--1.0.0--stable.sql(placeholder comment only) are removed here, and the return-to-stablePR aftermake tagbringsdefault_versionand the placeholder back.make verify-resultspasses on PG17;git ls-files | grep -e '--stable'andgit archive HEADboth show no--stablefile.