run-vcpkg@v7 - include the image OS and version in the cache's key

Changes:

• the cache's key format changed in order to include the image OS and its version. The change of the key content is a breaking change: all existing cached artifacts need to be recreated. This fixes #69

Note: to keep your workflow up to date with bug and security fixes, just use the v7 branch to stay on the most recent v7.x version of this action, e.g., uses: lukka/run-vcpkg@v7

run-vcpkg v6.3

Fix for #72

run-vcpkg v6.2

Changes:

• before using an existing vcpkg's executable (e.g. when restored from cache), try to run it with vcpkg --version and verify the exitcode is zero. Otherwise, the vcpkg is built again (using the boostrap-vcpkg script). Fixes #69

Note: to keep your workflow up to date with bug and security fixes, just use the v6 branch to stay on the most recent v6.x version of this action, e.g., uses: lukka/run-vcpkg@v6

run-vcpkg v6.1

Changes:

• update the quickstart documentation to show how to properly use run-vcpkg and run-cmake to properly handle the vcpkg.json manifest file and cache the vcpkg artifacts.
• fix the cache's key computation, added unit tests.
• add new input for run-vcpkg to specify a user defined directory: additionalCachedPaths. Added workflow validation tests.
• document that the vcpkg.json manifest file must be used with setupOnly: true.
• consuming more recent version of dependencies.

Note: to keep your workflow up to date with bug and security fixes, just use v3 branch to stay on the most recent v3.x version of this action, e.g., uses: lukka/run-vcpkg@v6

run-vcpkg changes for supporting vcpkg.json manifest file

Changes:

• the output variable RUNVCPK_VCPKG_TRIPLET is always set, even in setupOnly:true mode;
• when setupOnly:true, caching happens at the end of the workflow (rather than at the end of the step execution).
• added documentation and sample on how to leverage the vcpkg.json manifest file.

run-vcpkg caches on step execution (not post-step anymore)

The run-vcpkg version v5 action saves in cache the vcpkg generated artifacts during its step execution, rather than scheduling a caching job at the end of the workflow. This satisfies #24.
Other changes:

• consuming latest stable v1.0.x of the run-cmake-vcpkg-action-libs packages.
• cache restoring is attempted twice (fix for #50).

In order to get automatically updates (fix and security ones), in the workflow use the latest version like this: uses: lukka/run-vcpkg@v5.

Security fix service release for run-vcpkg@v4

Version v4.1 is a service release for fixing security issue on branch v4,

• bumped @actions/core to 1.2.6 to include security fixes;
• all dependencies provided by lukka/run-cmake-vcpkg-action-libs have been updated to include security fixes;

Note: just use v4 branch to stay on the most recent v4.x version of this action.

Code refactored to use NPM packages from https://github.com/lukka/run-cmake-vcpkg-action-libs

No new functionality.

Code has been refactored to leverages NPM packages published from: https://github.com/lukka/run-cmake-vcpkg-action-libs

The initially created solution based on a common Git submodule for sharing code among multiple GitHub Actions and Azure DevOps tasks has been dropped!

Now using NPM packages it is easier than ever to contribute by adding new features or fix bugs.

All unit tests have been moved into the NPM packages repository.

Add 'doNotCache' input

v3.3

add input to disable cache

Add triplet to cache's key when provided

When the vcpkgTriplet input is provided, add its content to the cache's key.