Skip to content

Releases: amacneil/dbmate

v1.14.0

04 Feb 05:15
519f186
Compare
Choose a tag to compare

Changed

  • Make status command read only (#242)

Fixed

  • Fix whitespace issues in SQLite absolute paths in DATABASE_URL (#266)
  • Append .exe to Windows release builds (#270)

Testing & Docs

  • Add scoop install instructions for windows (#263)
  • sqlite: Add test for two slashes in URL (#269)

v1.13.0

18 Jan 18:07
5cd9e25
Compare
Choose a tag to compare

v1.12.1

22 Jul 22:42
511336d
Compare
Choose a tag to compare

v1.12.0

07 Apr 20:57
b020782
Compare
Choose a tag to compare
  • Ability to specify custom --migrations-table (#178)
  • MySQL: Support + character in passwords (#200)
  • ClickHouse: Support non-UTC timezones (#208)
  • More helpful "invalid url" error message (#202)
  • Go v1.16 (#196)
  • Support custom logger when used as a library (#195)
  • Refactor drivers into separate packages (#179)

v1.11.0

19 Nov 04:58
61771e3
Compare
Choose a tag to compare
  • Added --migrations-table flag to specify custom schema_migrations table (#178)
  • PostgreSQL: Support custom schema (search path) using search_path URL parameter (#167, #169, #166)
  • MySQL: Create the schema_migrations table using latin1 charset to avoid index length limits with utf8mb4 (#172)
  • Go v1.15 and additional linters (#161, #165, #170)
  • Refactored drivers into separate packages (#179)

Backwards compatibility note: If you are using PostgreSQL with the (previously undocumented) search_path parameter in your URL, you will need to take action depending on the desired location of your schema_migrations table:

Prior to dbmate v1.11, the schema_migrations table was always stored in the public schema. Going forward, dbmate will always store schema_migrations in the first schema of your search_path.

If you wish to adopt the new behavior, you need to manually move your schema migrations table to the first schema in your search_path:

ALTER TABLE public.schema_migrations SET SCHEMA myschema

Alternatively, you can force dbmate to continue storing the migrations table in the public schema by using the --migrations-table "public.schema_migrations" CLI flag.

If you are only using the default (public) schema and did not specify a search_path in your URL, no action is necessary.

v1.10.0

13 Aug 15:32
616c4fe
Compare
Choose a tag to compare
  • Add ClickHouse support (#140)
  • Add --url flag (#150)
  • Allow setting most flags via environment variables (#152)
  • Add sql clients (and therefore support dbmate dump) in docker image (#157)
  • Upgrade dependencies (#148, #149)
  • Build statically linked binaries (#156)
  • Add linux/arm64 build (#155)

v1.9.1

19 Jul 22:24
8234882
Compare
Choose a tag to compare
  • Redact passwords in error messages (#145)

v1.9.0

25 Jun 21:07
2b61b43
Compare
Choose a tag to compare
  • Support for unix sockets with PostgreSQL and MySQL (#131, #136)
  • Add --verbose output flag to print last insert ID and rows affected (#138)
  • Add --wait-timeout flag (#127)

v1.8.0

29 Apr 00:25
a45d03a
Compare
Choose a tag to compare
  • Add dbmate status command to list applied and pending migrations (#120, #124)
  • Add --wait flag to all commands to wait for the database to be ready before proceeding (#112)
  • Fixed integration test failures with latest docker postgres images due to unset default password (#121)
  • Improved code linting (#113)

v1.7.0

25 Sep 05:11
e5ade06
Compare
Choose a tag to compare
  • Publish binaries for Windows and macOS (#89)
  • Fix dbmate wait command on PostgreSQL servers with no postgres schema (#90)
  • Improve error messages while loading .env files (#80)
  • Build with Go 1.13 (#89)