feat: support multiple versions of the pgrouting extension #1687
Conversation
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
hunleyd
previously requested changes
Aug 27, 2025
Contributor
hunleyd
left a comment
hunleyd
left a comment
There was a problem hiding this comment.
rebase to fix conflicts?
jfroche
force-pushed
the
multi-version-ext/pgrouting
branch
from
8dda7e0 to
b4659bc
Compare
samrose
force-pushed
the
multi-version-ext/pgrouting
branch
2 times, most recently
from
f7f6917 to
f6596bd
Compare
Build multiple versions of the pgrouting extension on different PostgreSQL versions. Add test for the extensions and their upgrade on PostgreSQL 15 and 17.
Test pgrouting upgrade path on orioledb-17
samrose
force-pushed
the
multi-version-ext/pgrouting
branch
from
e78106c to
df73191
Compare
samrose
approved these changes
Oct 6, 2025
Collaborator
samrose
left a comment
samrose
left a comment
There was a problem hiding this comment.
tested and ready to merge
hunleyd
added a commit
that referenced
this pull request
Oct 14, 2025
* origin/develop: fix(nix): remove '%' character from Nix trusted-public-keys configuration (#1840) chore: systemd hardening (#1837) Revert "refactor(postgresq): switch to 'include_dir' and then rename conf files to ensure ordering" (#1835) refactor(ansible): bring our ansible up to modern ansible-lint standards (#1821) fix(pgmq): replace drop_queue function if exists (#1828) refactor(postgresq): switch to 'include_dir' and then renames conf files to ensure ordering (#1820) feat: support multiple versions of the pg_jsonschema extension (#1757) feat: bump auth to v2.180.0 (#1829) feat: update supautils confs w/ new tables feat(migrations): predefined role grants (#1815) feat: run pg_regress tests after installing the last version of the extension (#1826) fix(pgmq): add missing helper function in migration script (#1825) feat: support multiple versions of the pgmq extension (#1668) feat: run pg_regress during extension tests (#1812) feat: support multiple versions of the pgrouting extension (#1687) refactor(ansible): bring our ansible up to modern ansible-lint standards (#1819) feat: support multiple versions of the pg-graphql extension (#1761)
encima
pushed a commit
that referenced
this pull request
Oct 28, 2025
* feat: support multiple versions of the pgrouting extension Build multiple versions of the pgrouting extension on different PostgreSQL versions. Add test for the extensions and their upgrade on PostgreSQL 15 and 17. * feat: run pgrouting pg_regress tests from nixos test VM * feat: test pgrouting with orioledb-17 Test pgrouting upgrade path on orioledb-17 * fix: we won't include an upgrade of pgrouting quite yet * fix: integration tests need updating to use postgis-all * chore: suffix to test * chore: bump version to release * chore: bump to release again` --------- Co-authored-by: Sam Rose <[email protected]>
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.
Build multiple versions of the pgrouting extension on different PostgreSQL versions.
Add test for the extensions and their upgrade on PostgreSQL 15 and 17.
Run pg_regress for pgrouting before and after upgrade.