OpenParable
Skip to content
← Back to skills

Bump Migration

Development
bump-migration

Bump Migration is an Agent Skill for development published in the fleetdm/fleet repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Bump a database migration's timestamp to the current time. Required when a PR's migration is older than one already merged to main. Use when asked to "bump migration", "update migration timestamp", or when a migration ordering conflict is detected.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/fleetdm/fleet/blob/HEAD/.claude/skills/bump-migration/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/bump-migration, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Bump a database migration timestamp

Bump the migration: $ARGUMENTS

When to use

This is required when a PR has a database migration with a timestamp older than a migration already merged to main. This happens when a PR has been pending merge for a while and another PR got merged with a more recent migration.

Process

1. Identify the migration to bump

If the user provided a filename, use that. Otherwise, find migrations on this branch that are older than the latest on main:

# List migrations on this branch that aren't on main
git diff origin/main --name-only -- server/datastore/mysql/migrations/tables/

2. Run the bump tool

The tool lives at tools/bump-migration/main.go. Run it from the repo root:

go run tools/bump-migration/main.go --source-migration YYYYMMDDHHMMSS_MigrationName.go

This will:

  • Rename the migration file with a new current timestamp
  • Rename the test file (if it exists)
  • Update all function names inside both files (Up_OLDTS → Up_NEWTS, Down_OLDTS → Down_NEWTS, TestUp_OLDTS → TestUp_NEWTS)

3. Optionally regenerate the schema

If the migration affects the schema, add --regen-schema to also run make dump-test-schema:

go run tools/bump-migration/main.go --source-migration YYYYMMDDHHMMSS_MigrationName.go --regen-schema

4. Verify

  • Check that the old files are gone and new files exist with the updated timestamp
  • Verify the function names inside the files match the new timestamp
  • Run go build ./server/datastore/mysql/migrations/... to check compilation

Rules

  • Always run from the repo root
  • Provide the migration filename, not the test filename
  • The tool handles both the migration and its test file automatically