Migration 0048 renamed into a duplicate key because the new controller's seeding had already inserted mesh-artifact-store; the control node's prepare fails on every apply since #171 rolled. Now: if the new row exists, move the holding and drop the old row; else rename. Merging at once: it unblocks the control node.
Migration 0048 renamed into a duplicate key because the new controller's seeding had already inserted `mesh-artifact-store`; the control node's prepare fails on every apply since #171 rolled. Now: if the new row exists, move the holding and drop the old row; else rename. Merging at once: it unblocks the control node.
A controller whose defaults carry the new name seeds it before the migration runs, and the first
form renamed into a duplicate key; the control node's prepare failed on every attempt (2026-09-30).
If the new row exists, the old row's holding moves to it and the old row goes; otherwise it is
renamed. The old name becomes an alias either way.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Migration 0048 renamed into a duplicate key because the new controller's seeding had already inserted
mesh-artifact-store; the control node's prepare fails on every apply since #171 rolled. Now: if the new row exists, move the holding and drop the old row; else rename. Merging at once: it unblocks the control node.