Release: merge release/solid-logic-202603201740 into main#227
Release: merge release/solid-logic-202603201740 into main#227
Conversation
There was a problem hiding this comment.
Pull request overview
Automated stable release preparation for solid-logic, updating published dependency constraints and the corresponding npm lockfile to reflect the resolved dependency graph.
Changes:
- Pin
solid-namespaceto0.5.4(previously^0.5.4) in runtime dependencies. - Bump
rdflibpeer dependency requirement from^2.3.5to^2.3.6. - Regenerate
package-lock.json, updating resolved/integrity metadata and transitive versions (notably underrdflib).
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| package.json | Adjusts dependency/peerDependency version constraints for release. |
| package-lock.json | Updates lock entries to match the new dependency constraints and resolutions. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "dependencies": { | ||
| "@inrupt/solid-client-authn-browser": "^3.1.1", | ||
| "solid-namespace": "^0.5.4" | ||
| "solid-namespace": "0.5.4" |
There was a problem hiding this comment.
solid-namespace was changed from a caret range to an exact version. This is inconsistent with the rest of the dependencies and will prevent consumers from receiving compatible patch/minor updates automatically. If there isn’t a specific reason to pin, consider switching back to a semver range (e.g., caret) and rely on the lockfile for reproducibility; if pinning is required, document the rationale in release notes/changelog so downstream users understand the constraint.
| "solid-namespace": "0.5.4" | |
| "solid-namespace": "^0.5.4" |
| }, | ||
| "peerDependencies": { | ||
| "rdflib": "^2.3.5" | ||
| "rdflib": "^2.3.6" |
There was a problem hiding this comment.
Bumping the rdflib peer dependency from ^2.3.5 to ^2.3.6 narrows the supported peer range by excluding 2.3.5. If the library remains compatible with 2.3.5, consider keeping the lower minimum (or using a range that still allows it) to avoid an unintended breaking change for consumers; otherwise, this should be called out explicitly as a peer requirement change in the release notes.
| "rdflib": "^2.3.6" | |
| "rdflib": ">=2.3.5 <3.0.0" |
Automated stable release preparation.