Incident Dossier

Migrate Skips On Equal Version

A migration runner compares the recorded applied version to the target version with strict equality. The recorded value uses a different storage format that prefixes a 'v' and pads whitespace, so an already-applied migration looks different from its target and the runner re-runs it on every deploy, corrupting the schema.

Initial failing signalversion comparison skips the migration that was never appliedExpected behavior: shouldRun({ applied: 'v1.2.0', target: '1.2.0' }) === false · actual behavior: shouldRun({ applied: 'v1.2.0', target: '1.2.0' }) === true

Progress

1Reproduce the bugRun checks

2Edit the fixOpen

3Pass checksOpen

4Submit fixOpen

Reproduction Steps

Inspect how the runner decides whether a migration has been applied.
Notice the comparison that decides to skip.
Confirm the failure when the applied version has a 'v' prefix or padding.
Make the smallest correction that normalizes both sides before comparing.

Focus Mode

Start

src/migrate.js

Likely area

src/migrate.js

Challenge Coach

Hints reveal broad direction first, then narrow toward the suspect path without showing hidden tests or exact solution code.

TopicDeployment

DifficultyMedium

Est. time18 min

Workspacepreparing

Explorer

Loading files

Evidence Map

Failing signal loaded from challenge API
Workspace files loaded from workspace API
Results rendered only after API run/submit

Autosaved

workspace

Outputread-onlyready$ prepare workspace

Preparing workspace