Skip to content

Release 1.1.0 - #66

Merged
jnasbyupgrade merged 3 commits into
Postgres-Extensions:masterfrom
jnasbyupgrade:release-1.1.0
Oct 30, 2026
Merged

jnasbyupgrade merged 3 commits into
Postgres-Extensions:masterfrom
jnasbyupgrade:release-1.1.0

Conversation

@jnasbyupgrade

@jnasbyupgrade jnasbyupgrade commented Oct 30, 2026 •

Copy link
Copy Markdown
Contributor

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 ... UPDATE to do.

default_version is pinned to 1.0.0 for the tag. The release carries no --stable scripts: sql/count_nulls--stable.sql (generated install script) and sql/count_nulls--1.0.0--stable.sql (placeholder comment only) are removed here, and the return-to-stable PR after make tag brings default_version and the placeholder back.

make verify-results passes on PG17; git ls-files | grep -e '--stable' and git archive HEAD both show no --stable file.

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.
@coderabbitai

coderabbitai Bot commented Oct 30, 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
  • 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: bfd81bb2-784c-4f50-80c9-967dd4c2bc30

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

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

@github-actions

github-actions Bot commented Oct 30, 2026 •

Copy link
Copy Markdown

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


Code review: no issues found

  • Distribution version is 1.1.0 in META.json and META.in.json. The extension provides version and default_version both stay at 1.0.0, which matches the PR description.
  • sql/count_nulls--1.0.0.sql exists, so pinning default_version = '1.0.0' works.
  • .gitattributes has sql/*--stable.sql export-ignore, which matches both count_nulls--stable.sql and count_nulls--1.0.0--stable.sql.
  • The HISTORY.md entry is clear.

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 default_version = 'stable' after make tag.

The release commit carries no *--stable* files; the return-to-stable PR after the tag re-seeds them. export-ignore is no longer needed.
@github-actions

github-actions Bot commented Oct 30, 2026 •

Copy link
Copy Markdown

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


Code review: no blocking issues

  • META.json and META.in.json set the distribution version to 1.1.0. The extension provides version stays at 1.0.0.
  • count_nulls.control pins default_version = '1.0.0', and sql/count_nulls--1.0.0.sql exists.
  • The HISTORY.md entry is clear.
  • The --stable scripts are deleted outright, so the tag has none. This matches the latest commit, "Remove --stable scripts and .gitattributes from the release".

Two notes, neither blocking:

  • The PR description still says a root .gitattributes marks sql/*--stable.sql as export-ignore. That file no longer exists in the branch, because the scripts are deleted instead. Update the description to match.
  • The follow-up PR after make tag must restore default_version = 'stable', restore sql/count_nulls--stable.sql and sql/count_nulls--1.0.0--stable.sql, and add a stable heading back to HISTORY.md.

I didn't build or run the tests.

@github-actions

github-actions Bot commented Oct 30, 2026 •

Copy link
Copy Markdown

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


Code review: no issues found

  • META.json and META.in.json set the distribution version to 1.1.0.
  • count_nulls.control pins default_version = '1.0.0'. sql/count_nulls--1.0.0.sql is tracked in git, so the pinned install script ships.
  • The --stable scripts are deleted outright, so the tag has none.
  • The HISTORY.md entry is clear.

The follow-up PR after make tag needs to restore default_version = 'stable', sql/count_nulls--stable.sql and sql/count_nulls--1.0.0--stable.sql, and the stable heading in HISTORY.md.

I didn't build or run the tests. The review is based on the diff and the repo files.

@jnasbyupgrade
jnasbyupgrade merged commit 069a0a4 into Postgres-Extensions:master Oct 30, 2026
29 checks passed
@jnasbyupgrade
jnasbyupgrade deleted the release-1.1.0 branch October 30, 2026 22:11
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