chore(api): adjust migration timestamp metadata for a1b2c3d4e5f6#36910
Merged
QuantumGhost merged 1 commit intoJun 2, 2026
Merged
Conversation
Assisted-by: Codex:GPT-5.4
Contributor
Pyrefly Type Coverage
|
QuantumGhost
changed the title
QuantumGhost
requested review from
MRZHUH,
laipz8200 and
snakevash
as code owners
dosubot
Bot
added
the
size:XS
FFXN
approved these changes
Jun 2, 2026
wylswz
approved these changes
Jun 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
AI disclosure: This PR was primarily drafted with Codex using GPT-5.4. I have reviewed and edited the final diff, and I am responsible for the content.
Closes #36909.
Summary
a1b2c3d4e5f6to use the UTC timestamp prefix2026_06_01_0610Create Dateto2026-06-01 06:10:00.000000Why
The revision is chained after
7885bd53f9a9(2026-05-27 09:53 UTC), but its filename and header still used an earlier timestamp from2026-04-11. That made the migration history inconsistent with the actual merge time and harder to inspect chronologically.The source PR was merged at
2026-06-01 14:10 +08:00, which is2026-06-01 06:10 UTC, so the migration metadata should use that UTC time.Impact
This is a metadata-only fix. It does not change the revision id,
down_revision, or schema behavior.