Skip to content

chore: release main - #210

Merged
piwi3910 merged 2 commits into
mainfrom
release-please--branches--main
Nov 16, 2026
Merged

piwi3910 merged 2 commits into
mainfrom
release-please--branches--main

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.16.0

0.16.0 (2026-11-16)

Parallel migration branches merge without conflicts: momo.sum has a new format 2 that git merges line by line, and the derived schema folds each migration against its own base, so independent branches validate and dependent ones fail at validate, never at apply. Standalone PostgreSQL sequences, additive CHECK value lists and primary-key updates are now modelled. Upgrade every binary that reads a migration directory together, since an older one refuses a format 2 momo.sum; follow docs/upgrading.md and docs/migrations.md. Changes since 0.15.0.

⚠ BREAKING CHANGES

  • migrate: momo.sum is written in format 2, one sorted checksum line per file under a # momo.sum format=2 header and no h1: directory hash; an older momo refuses it with migrate.ErrNewerFormat. momo migrate hash --sum-format 1 writes the old format for a fleet that cannot upgrade at once (#214, closes #205)

Features

  • migrate: two branches that each add migrations merge without a conflict when their changes are independent. With momo.sum merge=union in .gitattributes git merges momo.sum, and migrate hash and validate warn when the rule is missing. Branches that touch the same object, a view over a changed table, a foreign key's target, a sequence a default calls, an enum, extension or schema another change uses, or a function, trigger or policy body conflict at validate with ErrBranchConflict (#214)
  • migrate: momo migrate rebase --renumber [--applied] and Engine.Renumber move a pending branch that sorts before the newest applied version after it, writing the new files and momo.sum before removing the old ones; a migration it cannot move safely is named and refused before anything is written (#214)
  • migrate: standalone PostgreSQL sequences, such as one a column default calls with nextval, are part of the schema model. c.Sequence(name) declares one with Start, Increment, bounds, Cache and Cycle; migrate creates, alters and drops it, --from-db writes it, and drift reports an undeclared one as unmanaged: sequence. SQLite, MySQL and MariaDB refuse it with ErrUnsupported (#212, closes #207)
  • schema: c.CheckIn(&m.Kind, vals...) declares a CHECK over a list of values that migrate diff compares as a set, so adding a value is additive and removing one is flagged destructive by the check-value-removal lint rule; --from-db writes such constraints as CheckIn (#216, closes #206)
  • update: UpdateQuery.AllowKeyChange() lets Set assign a primary-key column on every dialect; a duplicate key is ErrUniqueViolation and an ON UPDATE CASCADE child follows the new key. Without it a key assignment is refused as before (#209, closes #204)
  • importer: the GORM, Bun and Ent importers write a composite index of the source model as a c.Index declaration, so a converted project no longer drops it on its next migration (#198)

Bug Fixes

  • migrate: the SQL splitter trims only the white space it scans and stops an identifier at a byte order mark, so a statement with non-ASCII white space is no longer split or rejoined differently from how PostgreSQL reads it (#201)

Performance Improvements

  • momotest: momotest.WithTemplateClone() builds the migrated schema once per server into a template database and gives each test its own clone, falling back to a schema per test when the role cannot create databases; without the option momotest.New is unchanged. sqlitetest.NewTemplate does the same for SQLite (#219, closes #167)

This PR was generated with Release Please. See documentation.

@github-actions
github-actions Bot force-pushed the release-please--branches--main branch 5 times, most recently from f4be0e0 to b23aebd Compare November 16, 2026 21:18
@github-actions
github-actions Bot force-pushed the release-please--branches--main branch from b23aebd to 3483eda Compare November 16, 2026 22:28
@piwi3910
piwi3910 merged commit 374d6c3 into main Nov 16, 2026
33 of 34 checks passed
@piwi3910
piwi3910 deleted the release-please--branches--main branch November 16, 2026 22:54
@github-actions

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment