Skip to content

chore: bump jsonld from 8.3.3 to 9.0.0#1280

Merged
straker merged 2 commits into
developfrom
jsonld-9
Feb 20, 2026
Merged

chore: bump jsonld from 8.3.3 to 9.0.0#1280
straker merged 2 commits into
developfrom
jsonld-9

Conversation

@straker
Copy link
Copy Markdown
Contributor

@straker straker commented Feb 16, 2026

Manual upgrade as #1255 was stuck on couldn't resolve conflicts.

No QA required

@straker straker requested a review from a team as a code owner February 16, 2026 23:40
@straker straker requested a review from chutchins25 February 16, 2026 23:40
Copy link
Copy Markdown

@chutchins25 chutchins25 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. Simple enough. Always interesting when there is a dependency that is not included.

@straker straker merged commit 7752f8c into develop Feb 20, 2026
30 checks passed
@straker straker deleted the jsonld-9 branch February 20, 2026 15:07
@Garbee Garbee mentioned this pull request Mar 4, 2026
straker pushed a commit that referenced this pull request Mar 5, 2026
The lockfile got out of sync, in a very odd way. I think npm broke
something in a minor in relation to how lockfiles get generated.

## The Problem

When [jsonLd](#1280) was
updated, something about it [broke the
builds](https://github.com/dequelabs/axe-core-npm/actions/runs/22229286256/job/64304204390).
But only after getting up to the publish point. The [Node
24](#1281) upgrade got in
fine, because it was probably slightly out of sync with `develop`.

## The Solution

Update to latest npm with `npm install -g npm` and then `npm install` to
refresh the lockfile. Now encoding shows up. This 100% did not work
before with an older NPM. So there is a break somewhere in expectations.

I narrowed it down to [npm
11.10.1](https://github.com/npm/cli/releases/tag/v11.10.1) that is where
`encoding` started to get pulled in. Due to some "hosting" in that
changelog, I'm wondering if this is a break from them moving
dependencies around.


No QA Required
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants