-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
[CLI] Bump CLI version to 2.0.0 #8416
Conversation
Thanks for this, we'll coordinate a release soon. |
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.
Ok I see. Looks like my PR from last week got committed right before #8346
I can coordinate another patch release today.
crates/aptos/CHANGELOG.md
Outdated
|
||
## [1.0.15] - 2023/05/29 |
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.
## [1.0.15] - 2023/05/29 | |
## [1.0.15] - 2023/05/30 |
I can patch another release today. Can we upate this to 5/30? Thanks!
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.
@alnoki or feel free to update the date to the "current" date. I will path a release when this PR is merged.
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.
We just spoke offline. We should bump the major version due to the breaking change with arg parsing for executing move functions.
@0xjinn 778728c updates the date to current per your request
@banool breaking arg parsing changes were already incorporated in the aptos move run \
--function-id $ace_addr::cli_args::set_vals \
--type-args \
0x1::account::Account \
0x1::chain_id::ChainId \
--args \
u8:123 \
"bool:[false, true, false, false]" \
'address:[["0xace", "0xbee"], ["0xcad"], []]' \
--private-key-file ace.key \
--assume-yes But I can not run the following JSON input file alternative, support for which was added in #8346: aptos move run \
--json-file entry_function_arguments.json \
--private-key-file ace.key \
--assume-yes Hence if you want to bump the version major then I think I think a retroactive re-release would be confusing, though, and I would prefer to just bump per how this PR currently stands, but can of course accommodate a re-release if that's what it takes to land the multisig tooling in a way that can be Please advise |
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.
Feel free to just land this. I can update the version on my end - since I have a PR that I want to commit before next release
Yeah late is better than never, we should've gone to 2.0.0 to begin with but now is okay still. I agree we should still have a section in the changelog for 1.0.14 though since we did indeed make that release. Not a big deal though. |
@banool 9088594 re-inserts Is this ready to land? |
@alnoki Yep go for it. Thank you for working on this and catching the conflict from 1.0.14! |
I just hit auto merge, it should land once all the land-blocking tests pass! |
@banool it looks like the CI is getting caught up here. Is there anything else I can do to move things along? |
Yeah we've had a couple of CI issues lately. The one that is blocking land right now is resolved, could you rebase? |
aptos-labs#8416 (comment) Squashed commit 1: Bump CLI version to 1.0.15 Squashed commit 2: Update current release date, Cargo.lock Squashed commit 3: Modify for v2.0.0 release Squashed commit 4: Re-insert v1.0.14 changelog section per @banool aptos-labs#8416 (comment)
Head branch was pushed to by a user without write access
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
✅ Forge suite
|
These failing tests are non-blocking and known to be having issues, don't worry about those. Once these other ones finish it should merge and we can make a release! |
✅ Forge suite
|
✅ Forge suite
|
@0xjinn now that the changelog and manifest version have been updated, are you able to coordinate a release tag so that |
@banool sounds like a plan. I missed this comment in the above forge logs, but I'm ready for a release when you are! Standing by to |
* Rebase per @banool #8416 (comment) Squashed commit 1: Bump CLI version to 1.0.15 Squashed commit 2: Update current release date, Cargo.lock Squashed commit 3: Modify for v2.0.0 release Squashed commit 4: Re-insert v1.0.14 changelog section per @banool #8416 (comment) * Remove erroneous double cash sign
* Rebase per @banool #8416 (comment) Squashed commit 1: Bump CLI version to 1.0.15 Squashed commit 2: Update current release date, Cargo.lock Squashed commit 3: Modify for v2.0.0 release Squashed commit 4: Re-insert v1.0.14 changelog section per @banool #8416 (comment) * Remove erroneous double cash sign
@0xjinn @banool @msmouse @areshand
In #8346 I bumped the changelog per the request of @banool and accordingly bumped the CLI
Cargo.toml
tov1.0.14
.It looks like #8398 duplicated some of this activity in a manner that did not introduce merge conflicts, but nevertheless instigated duplicate changelog headings, and led to the content from #8346 being excluded from the
v1.0.14
release.Hence this PR deduplicates the changelog headings, by bumping the CLI version to incorporate content from #8346 that was not included in the
v1.0.14
release.