Repository navigation
chore: release main - #210
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
5 times, most recently
from
November 16, 2026 21:18
f4be0e0 to
b23aebd
Compare
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
from
November 16, 2026 22:28
b23aebd to
3483eda
Compare
Contributor
Author
|
🤖 Created releases: 🌻 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release beep boop
0.16.0
0.16.0 (2026-11-16)
Parallel migration branches merge without conflicts:
momo.sumhas 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 2momo.sum; follow docs/upgrading.md and docs/migrations.md. Changes since 0.15.0.⚠ BREAKING CHANGES
momo.sumis written in format 2, one sorted checksum line per file under a# momo.sum format=2header and noh1:directory hash; an older momo refuses it withmigrate.ErrNewerFormat.momo migrate hash --sum-format 1writes the old format for a fleet that cannot upgrade at once (#214, closes #205)Features
momo.sum merge=unionin.gitattributesgit mergesmomo.sum, andmigrate hashandvalidatewarn 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 atvalidatewithErrBranchConflict(#214)momo migrate rebase --renumber [--applied]andEngine.Renumbermove a pending branch that sorts before the newest applied version after it, writing the new files andmomo.sumbefore removing the old ones; a migration it cannot move safely is named and refused before anything is written (#214)nextval, are part of the schema model.c.Sequence(name)declares one withStart,Increment, bounds,CacheandCycle;migratecreates, alters and drops it,--from-dbwrites it, anddriftreports an undeclared one asunmanaged: sequence. SQLite, MySQL and MariaDB refuse it withErrUnsupported(#212, closes #207)c.CheckIn(&m.Kind, vals...)declares a CHECK over a list of values thatmigrate diffcompares as a set, so adding a value is additive and removing one is flagged destructive by thecheck-value-removallint rule;--from-dbwrites such constraints asCheckIn(#216, closes #206)UpdateQuery.AllowKeyChange()letsSetassign a primary-key column on every dialect; a duplicate key isErrUniqueViolationand anON UPDATE CASCADEchild follows the new key. Without it a key assignment is refused as before (#209, closes #204)c.Indexdeclaration, so a converted project no longer drops it on its next migration (#198)Bug Fixes
Performance Improvements
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 optionmomotest.Newis unchanged.sqlitetest.NewTemplatedoes the same for SQLite (#219, closes #167)This PR was generated with Release Please. See documentation.