-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Getting stuff cleaned up and settled;
- Loading branch information
1 parent
7ea3c38
commit 1d57fcc
Showing
12 changed files
with
30 additions
and
51 deletions.
There are no files selected for viewing
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,14 @@ | ||
## v2.0.0 | ||
### Added | ||
* Set Use to clear previous ACL tokens when called to avoid conflicts | ||
* Caching, the way it should have been from the beginning. | ||
* Ensuring we include the version during builds | ||
* Adding more testing for commands | ||
* `--detailed` flag to `list` with colored output | ||
* `self update` command added to allow pulling in the latest version | ||
### Changed | ||
* Changed the naming of assets on releases to match more of what Go provides built-in | ||
### Fixed | ||
* Fixed bug where cache setting was not actually being checked | ||
* Removed print statement in use that caused eval to fail | ||
* Fixing an issue where running `use` could error out due to there not being any cached data |
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