Skip to content
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.

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

fix: set epoch to 3.1 in Clarity DB #5561

Merged
merged 4 commits into from
Dec 16, 2024
Merged

fix: set epoch to 3.1 in Clarity DB #5561

merged 4 commits into from
Dec 16, 2024

Conversation

obycode
Copy link
Contributor

@obycode obycode commented Dec 11, 2024

This is replacing #5559 as a hot fix against master instead of develop.

@obycode obycode requested a review from a team as a code owner December 11, 2024 15:47
@obycode obycode requested review from jcnelson and jferrant December 11, 2024 15:47
jferrant
jferrant previously approved these changes Dec 11, 2024
@obycode
Copy link
Contributor Author

obycode commented Dec 12, 2024

Oops, I merged in develop. Let me undo that...

@obycode
Copy link
Contributor Author

obycode commented Dec 12, 2024

Apologies for that mistake and the force-push to clean it up. I wanted to merge in the latest, but merged in develop instead of master.

Copy link
Member

@jcnelson jcnelson left a comment

Choose a reason for hiding this comment

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

This is now deployed and released, so let's get this merged 🙏

@wileyj wileyj merged commit 59f06b3 into master Dec 16, 2024
653 of 715 checks passed
@obycode obycode deleted the fix/31-transition branch December 16, 2024 21:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants