Invariant #1 violation: commits on main not in next
The release workflow's back-merge step failed silently (or
someone pushed to main without running hotfix-finish).
Until this resolves, the next live promotion's
git merge --ff-only will reject.
Commits on main missing from next (git log next..main)
38eb6ec chore: bump platform to v1.8.15
Fix
node scripts/release-promote.mjs hotfix-finish
Or manually:
git checkout next && git pull --ff-only
git merge origin/main --no-ff -m 'merge main into next (invariant restoration)'
git push origin next
This issue was opened by the invariant-sentry workflow
and will be auto-closed when the next run sees the
invariant restored.
Invariant #1 violation: commits on
mainnot innextThe release workflow's back-merge step failed silently (or
someone pushed to
mainwithout runninghotfix-finish).Until this resolves, the next live promotion's
git merge --ff-onlywill reject.Commits on
mainmissing fromnext(git log next..main)Fix
Or manually:
This issue was opened by the
invariant-sentryworkflowand will be auto-closed when the next run sees the
invariant restored.