Upgrade to pa11y@8
#161
Merged
Upgrade to pa11y@8
#161
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
10 tasks
danyalaytekin
force-pushed
the
use-pa11y-8
branch
from
0c5a1fe to
6e18849
Compare
danyalaytekin
added
type: maintenance
dependencies
danyalaytekin
changed the title
pa11y@8, and upgrade two dev deps to fix npm audit alertpa11y@8
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
pa11y@^8from^7ubuntu-latestinpublishWould become part of v5.
I'd hoped to smuggle in an upgrade to
eslint@9here, to fix an npm audit warning, but it turned out a bigger job than I'd thought. I'll wait for our linting configuration to become an ESLint Shareable Config first:eslint-config-pa11yeslint-config-pa11y#11This way we won't have to use the flat config converter in addition to any other changes (untested assumption).