chore(deps): bump n3 from 2.2.0 to 2.7.3 - #518
Conversation
Bumps [n3](https://github.com/rdfjs/N3.js) from 2.2.0 to 2.7.3. - [Release notes](https://github.com/rdfjs/N3.js/releases) - [Commits](rdfjs/N3.js@v2.2.0...v2.7.3) --- updated-dependencies: - dependency-name: n3 dependency-version: 2.7.3 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
dependabot
Bot
added
dependencies
davidwkeith
left a comment
davidwkeith
left a comment
There was a problem hiding this comment.
Reviewed against CONTRIBUTING.md. This is a routine Dependabot bump (n3 2.2.0 → 2.7.3) touching only packages/rdf/package.json and pnpm-lock.yaml.
Change itself: looks safe. 2.2.0 → 2.7.3 is all minor/patch releases per n3's own semver (new N3 parser features, store perf work, one parser bug fix) — no breaking changes flagged upstream, and @dwk/rdf's usage (Parser/Writer/DataFactory/Store in turtle.ts/store.ts/jsonld.ts) only exercises the stable public API surface, none of the touched internals.
CONTRIBUTING.md conformance:
- ❌ No changeset added for this
@dwk/rdf(publishable package) change — see inline comment for detail and precedent. ⚠️ PR body doesn't follow.github/PULL_REQUEST_TEMPLATE.md(Summary/Packages affected/Checklist) — this is Dependabot's default body, consistent with every prior dependency-bump PR in this repo's history, so not a new issue.- ✅ PR title
chore(deps): bump n3 from 2.2.0 to 2.7.3matches the Conventional Commits shape (type(scope): subject, lowercase, no trailing period) that this repo has consistently squash-merged for dependency PRs, even though thedepsscope isn't literally "package name minus@dwk/" per the letter of the convention. - CI was still in progress at review time (
build-test,integrationrunning); confirm green before merge.
None of this is new to this PR — it's the same shape as every previous automated dependency bump (e.g. #485). Worth a one-time decision on whether CONTRIBUTING.md should explicitly exempt automated dependency-only PRs from the changeset/template requirements, rather than each one nominally being out of conformance.
Generated by Claude Code
There was a problem hiding this comment.
Per CONTRIBUTING.md step 5, a changeset is required for "any user-visible change to a publishable package," and @dwk/rdf is publishable. n3 2.2.0 → 2.7.3 spans several feature/perf releases (N3 has/is-of/inverted-predicate parsing, bound-quad read optimizations) that are visible to consumers of @dwk/rdf's turtle.ts/store.ts wrappers, so this arguably isn't a "repo-only" change exempt from the changeset rule.
That said, this matches the precedent set by the prior n3 bump (#485, 2.1.1 → 2.2.0), which also merged without a changeset — so this looks like the established (if not strictly CONTRIBUTING.md-conformant) handling for Dependabot-authored dependency PRs in this repo rather than something new to this PR. Flagging for a maintainer call: either add a changeset here (pnpm changeset, patch bump for @dwk/rdf) or treat automated dependency-only bumps as changeset-exempt going forward and note that explicitly in CONTRIBUTING.md.
Generated by Claude Code
1 participant
Bumps n3 from 2.2.0 to 2.7.3.
Release notes
Sourced from n3's releases.
... (truncated)
Commits
30c108efix(parser): handle N3 verb edge cases (#719)ffb71f9perf(store): release bound quad read optimization (#718)a624b55Optimize bound quad reads (#708)a4b149dfix(ci): watch consumed RDF test suites (#715)210a1f8feat(parser): support N3 has, is-of, and inverted predicates (#694)8716681ci: validate merge queue commits (#716)fb1366cchore(ci): refetch upstream spec suites (#714)583d944chore(deps): Bump re-actors/alls-green from 1.2.2 to 1.3.0 (#713)1d8ef65chore(deps-dev): Bump the minor group with 4 updates (#712)46b2e4eperf: Optimize bound quad counts (#710)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)