| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| pgroll.macos.amd64 | 2026-01-05 | 26.3 MB | |
| pgroll_0.16.0_checksums.txt | 2026-01-05 | 427 Bytes | |
| pgroll.linux.amd64 | 2026-01-05 | 26.6 MB | |
| pgroll.linux.arm64 | 2026-01-05 | 25.3 MB | |
| pgroll.macos.arm64 | 2026-01-05 | 25.2 MB | |
| pgroll.win.amd64.exe | 2026-01-05 | 47.1 MB | |
| README.md | 2025-12-18 | 985 Bytes | |
| v0.16.0 source code.tar.gz | 2025-12-18 | 604.7 kB | |
| v0.16.0 source code.zip | 2025-12-18 | 752.8 kB | |
| Totals: 9 Items | 151.8 MB | 2 | |
🔴 Breaking changes
The create_index operation has changed to take the list of columns covered by the index as a list instead of a map:
Old format:
:::yaml
operations:
- create_index:
name: some-index
table: tickets
columns:
column1: {}
column2: {}
New format:
:::yaml
operations:
- create_index:
name: some-index
table: tickets
columns:
- column: column1
# options
- column: column2
# options
This is to ensure that the ordering of columns within in an index is stable (#1001).
This is a breaking change to the migration format. Use the pgroll update command to convert migrations containing create_index operations in the old format to use the new format, eg:
:::bash
pgroll update migrations/
Changelog
- [aee974] Fix
create_indexoperation column ordering (#1009)