Bump out-of-order migrations not included in v4.90.0

[lucasmrod]

Two migrations merged to main were not included in the v4.90.0 release but have timestamps older than 20260723181411_MultipleCustomPackagesPerTitle (the latest migration shipped in v4.90.0). Databases already on v4.90.0 would never apply them, since goose only runs migrations newer than the current (highest applied) version.

Bumped both to current timestamps via tools/bump-migration:

• 20260721090128_AddTokenInvalidToABMTokens → 20260806154139_AddTokenInvalidToABMTokens
• 20260721160351_AddHostMDMWindowsProfilesStatus → 20260806154150_AddHostMDMWindowsProfilesStatus

No schema or logic changes — only the file names, Up_/Down_/TestUp_ function names, and the regenerated schema.sql (migration_status_tables versions). Verified that none of the other unreleased migrations (20260724+) depend on the schema these two create, so applying them last is safe.

Checklist for submitter

If some of the following don't apply, delete the relevant line.

Testing

• Added/updated automated tests (existing migration tests renamed and re-run against MySQL)

Database migrations

• Checked schema for all modified table for columns that will auto-update timestamps during migration.
• Confirmed that updating the timestamps is acceptable, and will not cause unwanted side effects.
• Ensured the correct collation is explicitly set for character columns (COLLATE utf8mb4_unicode_ci).

Summary by CodeRabbit

• Database Updates
  • Added support for tracking whether ABM tokens are invalid.
  • Added Windows MDM profile status tracking and backfilled existing records.
• Maintenance
  • Updated database migration identifiers and status records to ensure migrations are applied consistently.
• Tests
  • Updated migration verification tests to match the revised migration identifiers.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 4891f2a3-15a0-4aed-801e-fd49483538f9

📥 Commits

Reviewing files that changed from the base of the PR and between b72d089 and adb8e2c.

📒 Files selected for processing (1)

• server/datastore/mysql/schema.sql

🚧 Files skipped from review as they are similar to previous changes (1)

• server/datastore/mysql/schema.sql

---

Walkthrough

Two MySQL migrations now use timestamps 20260806154139 and 20260806154150. Their registrations, exported functions, and test names were updated. The migration logic remains unchanged. The migration_status_tables seed data removes the previous migration identifiers and renumbers later rows.

Possibly related PRs

• fleetdm/fleet#48560: Renames and re-registers the same abm_tokens.token_invalid migration and related metadata.
• fleetdm/fleet#49849: Updates MySQL migration timestamps, names, tests, and status ordering.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the primary change: updating out-of-order migrations excluded from v4.90.0.
Description check	✅ Passed	The description explains the migration issue, lists affected migrations, documents the scope, and records relevant testing and database checks.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch bump-out-of-order-migrations-4.91

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[codecov]

Codecov Report

❌ Patch coverage is 66.66667% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 68.35%. Comparing base (25cfac3) to head (adb8e2c).

Files with missing lines	Patch %	Lines
...ables/20260806154139_AddTokenInvalidToABMTokens.go	66.66%	1 Missing ⚠️
.../20260806154150_AddHostMDMWindowsProfilesStatus.go	66.66%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #50690   +/-   ##
=======================================
  Coverage   68.35%   68.35%           
=======================================
  Files        3957     3957           
  Lines      254097   254097           
  Branches    13490    13490           
=======================================
+ Hits       173684   173688    +4     
  Misses      64859    64859           
+ Partials    15554    15550    -4     

Flag	Coverage Δ
backend	69.60% <66.66%> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.