-
Notifications
You must be signed in to change notification settings - Fork 6
/
release-notes.yaml
123 lines (113 loc) · 7.51 KB
/
release-notes.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
1.11.1:
version: 1.11.1
releaseNotes: |
* 🐛 Change package internal folder permisison issue after unzip
startPartition: 0
endPartition: 9
1.11.0:
version: 1.11.0
releaseNotes: |
* 🐛 Fix 403 error when downloading package from Github
* ✨ Login hook now supports any key value pair to be stored as a credential. Before it is limited to username, password, and token.
* 🚸 Ensure folder in the package have the correct permission.
* ⬆️ UUpdate cobra version to 1.7.0, viper version to 1.16.0
startPartition: 0
endPartition: 9
1.10.1:
version: 1.10.1
releaseNotes: |
* 🐛 Fix regression: flags aren't passed to `validArgsCmd` when `checkFlags` is true.
startPartition: 0
endPartition: 9
1.10.0:
version: 1.10.0
releaseNotes: |
* ✨ Support auto-complete for flag values. Introduced two new flag properties `values` for static flag values and `valuesCmd` for dynamic flag values.
* ✨ New `--list` option in the built-in rename command to list all command alias
* 🐛 Fix wrong exit code reported in metrics.
startPartition: 0
endPartition: 9
1.9.0:
version: 1.9.0
releaseNotes: |
* ✨New package level system command `__setup__`. This system hook can be triggered once a new package version is installed from the remote registry. Or manually triggered from the built-in `package setup` command.
* New configuration `enable_package_setup_hook` to toggle the new package setup hook during package installation
* New built-in command `package setup` to manually trigger the package setup system hook
* ✨New ways to define command flags. The newly introduced `flags` command property allows you to define the command flags with an object instead of the formatted string separated by `\t`. The `requiredFlags` property can be stilled be used to define flags, but it is marked as deprecated.
* ✨New `exclusiveFlags` command property to ensure that only one property can be specified among a set of flags. This property must be used together with the `checkFlags` property to delegate the command launcher for argument parsing
* ✨New `groupFlags` command property to ensure that all of them must be specified from the command line among a set of flags. This property must be used together with the `checkFlags` property to delegate the command launcher for argument parsing
startPartition: 0
endPartition: 9
1.8.1:
version: 1.8.1
releaseNotes: |
* 🐛 Fix DNS resolve issue on darwin amd64 under VPN. For Mac intel user, please download this version.
startPartition: 0
endPartition: 9
1.8.0:
version: 1.8.0
releaseNotes: |
* ✨Support multiple remote registry. From version 1.8.0, you are able to define multiple remote registries. Command launcher synchronizes the commands with all these remote registries at the end of each command execution. This is useful for several scenarios: for example, supporting internal or experimental commands, different teams target their commands to different group of audience.
* ✨Built-in command `remote` command to mange multiple remote registries.
* `remote list`: list all remote registries
* `remote delete`: delete specific remote registry
* `remote add`: add a new remote registry
* ✨Built-in package management related commands are regrouped into `package` command:
* `package list`: list installed local and dropin packages and remote packages. It also provides the possibility to show the installed commands
* `package install`: install dropin packages from git repository or remote/local zip file
* `package delete`: delete installed dropin packages
* ✨New command name conflict resolution system: Each command now has a unique full name in form of [regitry]@[package]@[group]@[name]. When two commands register to the same group and name. One of them will be registered with its full group name.
For example, two command `hello@greeting@pkg1@repo1` and `hello@greeting@pkg2@repo2`. These two commands have the same group name and command name (greeting hello). The first one will be registered as `cola greeting hello`, the second one will be registered as command `cola greeting@@pkg2@repo2 hello`. Note: `greeting@@pkg2@repo2` is the full name of the group command `greeting` defined in pkg2 and repo2.
* ✨New built-in `rename` command. Now it is possible to rename both group and sub command to a different name.
* ✨New resource `PACKAGE_DIR`. Each command now can access its package's absolute path through the `PACKAGE_DIR` resource. This resource doesn't require user consent.
* 🔥Metrics system hook interface change. Now the metrics system hook accepts two new parameters: repo/registry name, package name. The full list of parameters:
1. repository/registry name (see remote command)
2. package name
3. command group name, or “default” if no group
4. command name
5. user partition
6. command exit code
7. command execution duration in nano seconds
8. error message or “nil” if no error
9. command start timestamp in seconds
startPartition: 0
endPartition: 9
1.7.0:
version: 1.7.0
releaseNotes: |
* ✨New mechanism to access resources with user consent, resources required user consent:
* username
* password
* login_token
* log_level
* ✨New system package with system command. Now supports two types of system command:
* __login__: extends the built-in login command
* __metrics__: extends the built-in metrics
* ✨New package management with new built-in commands:
* list: list installed local and dropin packages and remote packages. It also provides the possibility to show the installed commands
* install: install dropin packages from git repository or remote/local zip file
* delete: delete installed dropin packages
* ✨New URL convention for command launcher self update. You can now use the Github release file as the latest version
* ✨New configurations:
* enable_user_consent
* user_consent_life
* system_package
* system_package_public_key
* system_package_public_key_file
* verify_package_checksum
* verify_package_signature
* 🔒️Enable package checksum verification
* ♻️Refactor local repository management and remote management
* 🔨Default local build version now takes the current branch name: [branch name]-dev. See build.sh
startPartition: 0
endPartition: 9
1.6.0:
version: 1.6.0
releaseNotes: |
- Add the PackageDir context variable to reference the package's directory, same as the Cache and Root context variables. Cache and Root variables are deprecated.
- Extend the format of the flag definition. Now it is possible to add bool type flags: [name] \t [shorthand] \t [description] \t [type] \t [default].
- New command definition field in manifest, checkFlags. The default value is false, when it is true, before executing the command, the arguments will be parsed, and the parsed flags and args will be passed to the command in form of an environment variable: [APP_NAME]_FLAG_[FLAG_LONG_NAME] and [APP_NAME]_ARG_[ARG_INDEX_STARTS_FROM_1]
- New command definition field in the manifest: argsUsage to customize the one-line help message. This field will take effect when checkFlags=true
- New command definition field in the manifest: examples to customize the examples in the help message. This field will take effect when checkFlags=true
startPartition: 0
endPartition: 9