tern 3.1.6

Embedded database migrations in SQL or Rust.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55

# Changelog

All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## 3.1.6 - 2026-08-05

### Fixed
* [[#45]]: Fixed syntax of SQLite history table DDL.

## 3.1.5 - 2026-04-27

### Fixed
* [[#38]]: Fixed issue with SQL migration sources that use `tern:noTransaction` where splitting
  the query into individual statements would produce invalid output in certain cases; closes [[#33]].


## 3.1.0 - 2025-05-21

### Added
* [[#26]]: Method `Runner::run_apply` and CLI subcommand that accepts a target version to apply migrations up through.
  * Validation rule that local migrations be a superset of remote history with respect to version and name.
  * Ability of the migration parent module to be of the `mod.rs` form.
  * `Display` impl for `Report`.

### Changed
* [[#26]]: Deprecated `Runner::apply_all` in favor of `run_apply_all` to accept `dryrun` argument.  Deprecated
  `Runner::soft_apply` and CLI subcommand in favor of `run_soft_apply` to not accept a `start_version` input.
  * Logging: All usage of `log::info!` changed to `log::trace!`. CLI returns the report for the user to render
    if they want.

### Fixed
* [[#26]]: Ignore hidden files in migration directory during `MigrationSource` proc macro expansion.
  * Error produced with invalid macro attribute path.
  * Internal logic for splitting statements in a `no_tx` scenario allows block comments `/* ... */`.

## 3.0.0 - 2025-01-17

### Added
* [[#24]]: Add validation when parsing migration versions during proc macro expansion and during
  execution for `apply-all` and `dryrun`.  Reject duplicate versions and missing versions.

### Changed
* [[#24]]: The `Migration` interface is changed to return the built migration query for the `dryrun`
  command so that it can be displayed in the report.  Similarly, a report "content" field
  now contains the query that was applied rather than the file content in a report coming
  from an `apply-all` operation.

[#24]: https://github.com/quasi-coherent/tern/pull/24
[#26]: https://github.com/quasi-coherent/tern/pull/26
[#33]: https://github.com/quasi-coherent/tern/issues/33
[#38]: https://github.com/quasi-coherent/tern/pull/38
[#45]: https://github.com/quasi-coherent/tern/pull/45