Bumping to latest Vally release and standardising on package.json version (#2535)

The workflows were doing their own vally installs, which means that we had the potential for drift in the version of Vally being used. Now we do a npm ci and get the version from there, removing the ambiguity
This commit is contained in:
Aaron Powell
2026-08-04 16:49:17 +10:00
committed by GitHub
parent d99609ee1a
commit dab758a392
4 changed files with 958 additions and 54 deletions
+1 -1
View File
@@ -39,9 +39,9 @@
"author": "GitHub",
"license": "MIT",
"devDependencies": {
"@microsoft/vally": "^0.12.0",
"ajv": "^8.20.0",
"ajv-formats": "^3.0.1",
"@microsoft/vally": "^0.6.0",
"all-contributors-cli": "^6.26.1"
},
"dependencies": {