|
| 1 | +## July 2023 Release (version 2.1.0) |
| 2 | + |
| 3 | +This release fixes several issues in **vs-secrets** and removes the need to create the encryption key and GitHub authorization in case you need to work only with Azure Key Vaults. |
| 4 | + |
| 5 | +### Changes |
| 6 | + |
| 7 | +* The **init** command can be used for regenerating the GitHub authorization in case it is missing or not valid. |
| 8 | +* It the encryption key already exists, the **init** command cannot be used for creating a new encryption key. Now a warning is displayed saying tha you should use the **change-key** command. |
| 9 | +* The **change-key** command has the new parameter -s (or --skipencryption) for skipping the re-encryption of secrets encrypted with the old key. |
| 10 | +* The **status** command show the number of projects in the solution that support secrets, but the secrets have not been setted. |
| 11 | +* The **status** command, by default will not show anymore solution duplicates. Two solutions are considered duplicates if they share the same secrets and the same secrets repository configuration. |
| 12 | +* The **status** command has the new parameter -d (or --duplicates) for showing also solution duplicates. |
| 13 | +* Improved output for the commands **configure list**, **pull**, **push**, **search**. |
| 14 | + |
| 15 | +### Fixes |
| 16 | + |
| 17 | +* Fixed behaviour in case the user want to use only Azure Key Vault. The absence of the the encryption key and the GitHub authorization does not block anymore the commands **status**, **push**, **pull** and **change-key**. |
| 18 | +* In some scenario the default repository used to be always GitHub. From this release the default repository is the one defined with the **configure --default** command. The GitHub repository remains the default in case no default repository has been defined with the command **configure --default**. |
| 19 | +* Fixed UTF8 encoded text output. |
| 20 | +* Fixed Azure Key Vault repository for when you use the --all parameter with the commands that support it. |
| 21 | + |
| 22 | +--- |
| 23 | + |
| 24 | +## July 2023 Release (version 2.0.2) |
| 25 | + |
| 26 | +This is a bug fixing release for the tool **vs-secrets** |
| 27 | + |
| 28 | +### Fixes |
| 29 | + |
| 30 | +* Fixed directory scanning in case one directory is inaccessible. |
| 31 | + |
| 32 | +--- |
| 33 | + |
1 | 34 | ## July 2023 Release (version 2.0.1) |
2 | 35 |
|
3 | 36 | This release fixes the vulnerability CVE-2023-29337. |
|
0 commit comments