Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

un-pin axe-core from 4.3.3

Description

Summary: Un-pin axe-core from "4.3.3", moving back to something like "^4.3.5".

Details: axe-core 4.3.4 causes test failures which are breaking the master-branch build dependency. Locking to 4.3.3 resolves the problem, but prevents us from getting future feature enhancements or bug fixes and should be reverted as soon as a non-broken release is published.

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Zak Burke September 30, 2022 at 4:26 PM

, I noticed these errors in a platform-complete build log while investigating another failure:

which dragged me back to this ticket, which is sorta related, since this issue has been fixed in axe-core but I remembered that we had pinned our version in the past. In stripes-testing, we are still locked onto axe-core 4.3.3. Shall I file a ticket to unpin it there, too? It's also at ~4.1.4 in eholdings.

Denys Bohdan May 11, 2022 at 1:07 PM

 this is a technical story so there's nothing on UI to test, I'll close it

Zak Burke April 22, 2022 at 12:58 PM

Correct, : this story is limited to unpinning, back to something like ^4.3.5. If we need to resolve new warnings that come from the new version, please file separate tickets for that work.

Denys Bohdan April 22, 2022 at 11:33 AM

 and  in scope of this story do we want to just unpin the versions and deal with the warnings in another story?

Khalilah Gambrell April 22, 2022 at 1:21 AM

, , and  is this something Spitfire can do?

Done

Details

Assignee

Reporter

Labels

Priority

Story Points

Sprint

Development Team

Spitfire

Fix versions

Release

Morning Glory (R2 2022)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created October 28, 2021 at 8:13 PM
Updated September 30, 2022 at 4:26 PM
Resolved May 11, 2022 at 1:07 PM
TestRail: Cases
TestRail: Runs