-
Notifications
You must be signed in to change notification settings - Fork 240
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 CHANGELOG #107
🔧 Fix CHANGELOG #107
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
were these actually all off by 1? 🤔 we have some PRs to automate this flow and improve |
Versions listed were:
|
ok, 6 is also missing but doesn't have to be solve here |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
actually, given 6 is missing, we should sanity check that all of these actually have the changes they say they do. E.g is writeFinalize... in 5 ?
CHANGELOG.md
Outdated
@@ -6,19 +6,19 @@ | |||
|
|||
- Export writeFinalizeWithdrawTransaction and fix getProveWithdrawalTransactionArgs | |||
|
|||
## 0.0.1-alpha.5 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Sabnock01 I think read finalizedWithdrawals first shows up here https://www.npmjs.com/package/op-viem/v/0.0.1-alpha.5?activeTab=code
I think possibly .2 was a no-op and the latest should have been .6, matching https://www.npmjs.com/package/op-viem/v/0.0.1-alpha.5?activeTab=versions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Got it. So the only issue was the most recent was incorrectly labeled .5
instead of .6
.
Fixes incorrect release versions in
CHANGELOG.md
.