Node.js database migration management for PostgreSQL
Full Changelog: https://github.com/salsita/node-pg-migrate/compare/v7.3.1...v7.3.2
Full Changelog: https://github.com/salsita/node-pg-migrate/compare/v7.3.0...v7.3.1
runner
is now also exported as named-export
this might become the default strategy for importing runner in a later major
Full Changelog: https://github.com/salsita/node-pg-migrate/compare/v7.2.2...v7.3.0
Full Changelog: https://github.com/salsita/node-pg-migrate/compare/v7.2.1...v7.2.2
salsita/node-pg-migrate
with write access, to help further with the documentation ❤️Full Changelog: https://github.com/salsita/node-pg-migrate/compare/v7.2.0...v7.2.1
Full Changelog: https://github.com/salsita/node-pg-migrate/compare/v7.1.0...v7.2.0
grant
and revoke
🎉Full Changelog: https://github.com/salsita/node-pg-migrate/compare/v7.0.0...v7.1.0
The core maintainer of this project moved to @Shinigami92 (also core maintainer of FakerJS and core member of Vite).
The project is and remains under the MIT license.
This version is a mostly compatible to v6.2.2, but (should) supports ESM in addition to CJS :tada: If you found any bugs while moving from version v6.2.2 to version v7.0.0, please open an issue and report what was broken for you. If you need to contact me somehow directly, you can do so on Mastodon @[email protected]
I (@Shinigami92) worked hard the last 1.5 month on refactoring node-pg-migrate
and I plan to convert the source code to ESM in the next major version. However I will need to drop support for Node <18 and TS <5 for that. So the next major version could potentially be released "quickly".
The code base is now stable to ship new features and fix more known bugs.
Migration.create
does not accept the deprecated params anymore #1002
if you did not ignored the runtime warning, you should not be affected by this
createSchemalize
function now uses options instead of two boolean args #1058
You should mostly not be affected by this, expect from extreme programmatic use-cases
utils
got restructured #1053
this should not have changed anything from the usage
src
folder got a bit restructure, so you should only be affected by breaking changes if you use node-pg-migrate progammatically (not CLI)ts-node
, tsconfig.json
's 'ts-node'
override is now respected (thx to @BriungRi)mkdirp
#1102 and decamilized
#1099
pgm
methods #1104
migration-builder
to migrationBuilder
) and used node:*
imports #1101
Full Changelog: https://github.com/salsita/node-pg-migrate/compare/v6.2.2...v7.0.0
mkdirp
#1102 and decamilized
#1099
pgm
methods #1104
migration-builder
to migrationBuilder
) and used node:*
imports #1101
Full Changelog: https://github.com/salsita/node-pg-migrate/compare/v7.0.0-alpha.3...v7.0.0-alpha.4
src
folder got a bit restructure, so you should only be affected by breaking changes if you use node-pg-migrate progammatically (not CLI)ts-node
, tsconfig.json
's 'ts-node'
override is now respected (thx to @BriungRi)Full Changelog: https://github.com/salsita/node-pg-migrate/compare/v7.0.0-alpha.2...v7.0.0-alpha.3