padmavemulapati
commented
1 year ago Validated with the latest canary build avaible for axe-core-nuget (4.7.2-alpha.49)
For Axe-core-nuget we are not externally/intenally keeping package.json to specify the dependencies. But whatever the version for axe-core is updated , axe-core-nuget is holding strictly that version. (which will not allow minor updates)
Playwright Holding axe-core 4.8.2
Selenium holding axe-core4.8.2
HelpURL also getting with axe/4.8/
Environment:
| Label | Value |
|---|---|
| Product | axe-core-nuget |
| Version | 4.7.2-alpha.49 |
| OS-Details | MAC- Intel Core i7 - 11.6.8 & Windows11 |
| BrowserDetails | Chrome Version 117.0.5938.88 (Official Build) (64-bit) & Firefox 117.0 |
A user recently ran into a problem where they installed an api at v4.7 but got axe-core version v4.8 (causing some confusion on why rules weren't running that should have been). Turns out that we've been pinning to axe-core using
^which allows minor updates. This goes against our goal of version locking the apis to the major and minor version of axe-core that is used in the api.We'll fix this by using an exact match to patch pin our axe-core dependency.