Skip to content

Latest commit

 

History

History
142 lines (84 loc) · 5.55 KB

CHANGELOG.md

File metadata and controls

142 lines (84 loc) · 5.55 KB

August 2024 Release (version 2.2.1)

  • Updated dependencies with vulnerabilities.

November 2023 Release (version 2.2.0)

Changes

  • Added support for .NET 8
  • Removed support for .Net Core 3.1 and .NET 7.

October 2023 Release (version 2.1.2)

This is a maintenance release.

Fixes

  • Updated dependencies for fixing security vulnerability CVE-2023-36414.

August 2023 Release (version 2.1.1)

This is a maintenance release.

Fixes

  • Fixed minor issues in exception handling.

August 2023 Release (version 2.1.0)

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.

Changes

  • The init command can be used for regenerating the GitHub authorization in case it is missing or not valid.
  • 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.
  • The change-key command has the new parameter -s (or --skipencryption) for skipping the re-encryption of secrets encrypted with the old key.
  • The status command show the number of projects in the solution that support secrets, but the secrets have not been setted.
  • 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.
  • The status command has the new parameter -d (or --duplicates) for showing also solution duplicates.
  • Improved output for the commands configure list, pull, push, search.

Fixes

  • 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.
  • 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.
  • Fixed UTF8 encoded text output.
  • Fixed Azure Key Vault repository for when you use the --all parameter with the commands that support it.

July 2023 Release (version 2.0.2)

This is a bug fixing release for the tool vs-secrets

Fixes

  • Fixed directory scanning in case one directory is inaccessible.

July 2023 Release (version 2.0.1)

This release fixes the vulnerability CVE-2023-29337.

October 2022 Release (version 2.0.0)

This release enables the use of different kinds of repositories and enables to configure each solution to use a different kind of repository.

Azure Key Vault is the new supported repository. Azure Key Vault is the recommended repository to use for scenarios where the solution secrets can be shared within the development team.

New Features

  • Added Azure Key Vault as an alternative repository for storing solution secrets.

  • New command: configure

    The "configure" command let to specify the default repository for your secrets (GitHub Gists or Azure Key Vault). Alternatively, with this command you can configure single solutions to use the preferred repository. Now you can have some solutions using GitHub Gists and some others using Azure Key Vault. It is possible to use different Azure Key Vault resources for different solutions, so, if you work with different development teams, each team can share their own secrets.

  • New command: configure list

    This command display the custom repository configuration for the solutions.

  • New command: clear

    The "clear" command erase the solution secrets from the local machine. It is equivalent to applying the command "dotnet user-secerts clear" for each project in the solution.

Changes

  • Changed status command. It has been enhanced for displaying the default repository and the custom repository configured for each solution. In addition it display the synchronization status between the local and remote secret settings.
  • The search command shows also the user secret id setted in the project file.
  • The command changekey has been renamed to change-key.

September 2022 Release (version 1.2.0)

Added new features and improvements.

Features

  • Added the new command "changekey". This command changes the encryption key locally e re-encrypts the remote secrects with the new key. Use this command if you loose the key or the key is compromised.
  • Extended the "status" command for displaying also the synchronization status of the solutions. The status command now has two new parameters: --path and --all.

Fixes

  • Fixed the management of relative paths passed to the --path parameter.
  • Fixed issues in the Windows/WSL Linux environment.
  • Minor fixes.

April 2022 Release (version 1.1.2)

Features

  • Extended secrets management to ASP.NET MVC 5 projects.
  • Added support to projects that share the same secret files.
  • Added "status" verb for checking the tool configuration.
  • Added check for upgrade to a new version.
  • Improved output presentation.

February 2022 Release (version 1.0.2)

Initial release. Tool for syncing Visual Studio solution secrets across different development machines.

Features

  • Searching for projects that use secrets.
  • Pushing encrypted secrets to a remote repository.
  • Pulling ecrypted secrets from a remote repository.
  • Implemented GitHub Gist as remote secrets repository.