Skip to content

fix: support non timestamp but numeric migrations #301

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 2 commits into from
Apr 4, 2025
Merged

fix: support non timestamp but numeric migrations #301

merged 2 commits into from
Apr 4, 2025

Conversation

psteinroe
Copy link
Collaborator

@psteinroe psteinroe commented Apr 4, 2025 •
edited
Loading

fixes #300

juleswritescode
juleswritescode approved these changes Apr 4, 2025
View reviewed changes
Copy link
Collaborator

@juleswritescode juleswritescode left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, but: Should we rename the timestamp property, since it's more of an ID now?

@psteinroe psteinroe merged commit 5d0c8e6 into main Apr 4, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@juleswritescode juleswritescode juleswritescode approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

add support for non-timestamp but still numeric migrations
2 participants
@psteinroe @juleswritescode