chore(deps)(deps): bump n3 from 1.26.0 to 2.1.0#1364
Conversation
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
dependabot
Bot
requested review from
Jurij89,
branarakic and
zsculac
as code owners
| "dependencies": { | ||
| "force-graph": "^1.51.0", | ||
| "n3": "^1.22.3", | ||
| "n3": "^2.1.0", |
There was a problem hiding this comment.
🟡 Issue: Align the runtime upgrade with the TypeScript contract
What's wrong
The PR moves graph-viz to an n3 v2 runtime while leaving the package compiled against @types/n3 1.26.x. That makes the dependency boundary harder to reason about: readers see a major runtime upgrade, but the declared TypeScript contract still looks tied to the previous major line.
Example
A future change can import an n3 v2 API shape while TypeScript is still checking against the older 1.26 type package, so the package boundary no longer clearly says which contract graph-viz is coded against.
Suggested direction
Treat the runtime dependency and type dependency as one boundary. Update or remove the companion @types/n3 dependency as appropriate, or make the intentional mismatch explicit so the next reader does not have to infer it.
Confidence note
I could not verify from local files whether n3 v2 is intentionally still typed by @types/n3 1.26.x. If that is the established upstream typing story, this can be waived, but the version boundary should be made explicit.
For Agents
Inspect packages/graph-viz/package.json and the n3 type source. Preserve the runtime upgrade, but either remove @types/n3 if v2 ships its own types, align the type package to a v2-compatible declaration if available, or document/pin why the 1.26 typings are the canonical contract. Run pnpm --filter @origintrail-official/dkg-graph-viz typecheck after the change.
Bumps [n3](https://github.com/rdfjs/N3.js) from 1.26.0 to 2.1.0. - [Release notes](https://github.com/rdfjs/N3.js/releases) - [Commits](rdfjs/N3.js@v1.26.0...v2.1.0) --- updated-dependencies: - dependency-name: n3 dependency-version: 2.1.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/n3-2.1.0
branch
from
7c7ca66 to
c7541e2
Compare
otReviewAgent
left a comment
otReviewAgent
left a comment
There was a problem hiding this comment.
Review Agent completed this review and found no issues.
1 participant
Bumps n3 from 1.26.0 to 2.1.0.
Release notes
Sourced from n3's releases.
Commits
4df0254feat: ship ESM browser bundle (#597)8ee97c8chore(deps): Bump actions/checkout from 6 to 7 (#606)4e4a5ebchore(deps-dev): Bump globals from 16.5.0 to 17.6.0 (#605)76c7435chore(deps-dev): Bump rdf-test-suite in the minor group (#603)eda236bchore(deps-dev): jest 30 (drops Node 14/16 from test matrix) (#599)bc8a879chore(deps-dev): eslint 10 + flat config (eslint-plugin-import-x) (#600)d8293efchore(deps-dev): Bump the minor group with 5 updates (#591)c1027ccfix: Disallow surrogate pairs - fixes #589 (#593)aaa5cb2chore(deps-dev): Bump@babel/preset-envin the minor group (#587)5686ab4chore(deps-dev): Bump pre-commit from 1.2.2 to 2.0.0 (#585)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for n3 since your current version.