🥳 ec2-instance-selector v2.0.0 Automated Release! 🥑 #122
Conversation
This file contains 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
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.
ec2-instance-selector v2.0.0 Automated Release! 🤖🤖
Release Notes 📝:
New Features 🎊 🥳
--memoryand--gpu-memory-totalas a byte quantity such as "4gb", "12tb", or "612mb". If you just specify an integer with no unit, ec2-instance-selector will default to use GiB. NOTE: the previous versions would always use MiB, so this is a breaking change. (accept memory and gpu memory in GiB instead of MiB amazon-ec2-instance-selector#36)Removals
--availability-zoneflag has been removed. This flag was previously deprecated in favor of the plural--availability-zonesflag which will do an intersection of instance types available in all of the availability zones given. (remove az for pending major release amazon-ec2-instance-selector#42)Tests
Other: