Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG: CLI getting installed with canary version but showing and working for Prod version(4.7.3) #857

Open
1 task done
padmavemulapati opened this issue Oct 6, 2023 · 1 comment
Labels
bug Something isn't working PRIORITY: low Low priority item; can be placed in backlog web-apis

Comments

@padmavemulapati
Copy link

Product

cli

Product Version

4.7.4-62fd241.0

Latest Version

  • I have tested the issue with the latest version of the product

Issue Description

Expectation

Installed canary version for axe-core/cli (4.7.4-62fd241.0) using npm install @axe-core/cli@next so that it should work for latest changes and axe --version should get the same version number

Actual

axe --version is giving 4.7.3 and working for Prod only

How to Reproduce

  1. Created a Directory and created a package.json using npm init -y
  2. Insalled axe-core/cli canary version ('npm install @axe-core/cli@next) (Installed gobally using -g and locally both)
  3. Package.json is showing canary version(4.7.4-62fd241.0)
  4. Run axe --version to make sure cli installed properly

Issue:
Getting 4.7.3 (Prod version)

image

Environment:

Label Value
Product axe-core-npm
Version 4.7.4-62fd241.0
OS-Details _MAC- Intel Core i7 - 11.6.8 & Windows11 _
VSCode Editor 1.82.2
@padmavemulapati padmavemulapati added bug Something isn't working PRIORITY: high High priority item; should be scheduled in this or next sprint labels Oct 6, 2023
@padmavemulapati
Copy link
Author

Regression done for CLI, it is showing version missmatch(4.7.3) but working for the canary version only(4.7.4-62fd241.0).

So lowering the priority as this is not blocking the release.

@padmavemulapati padmavemulapati added PRIORITY: low Low priority item; can be placed in backlog and removed PRIORITY: high High priority item; should be scheduled in this or next sprint labels Oct 11, 2023
This was referenced Oct 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working PRIORITY: low Low priority item; can be placed in backlog web-apis
Projects
None yet
Development

No branches or pull requests

4 participants