Skip to content

Release: merge release/solid-logic-202603201740 into main#227

Open
bourgeoa wants to merge 1 commit intomainfrom
release/solid-logic-202603201740
Open

Release: merge release/solid-logic-202603201740 into main#227
bourgeoa wants to merge 1 commit intomainfrom
release/solid-logic-202603201740

Conversation

@bourgeoa
Copy link
Contributor

Automated stable release preparation.

Copilot AI review requested due to automatic review settings March 20, 2026 17:41
@bourgeoa bourgeoa enabled auto-merge March 20, 2026 17:41
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

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-namespace to 0.5.4 (previously ^0.5.4) in runtime dependencies.
  • Bump rdflib peer dependency requirement from ^2.3.5 to ^2.3.6.
  • Regenerate package-lock.json, updating resolved/integrity metadata and transitive versions (notably under rdflib).

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"
Copy link

Copilot AI Mar 20, 2026

Choose a reason for hiding this comment

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

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.

Suggested change
"solid-namespace": "0.5.4"
"solid-namespace": "^0.5.4"

Copilot uses AI. Check for mistakes.
},
"peerDependencies": {
"rdflib": "^2.3.5"
"rdflib": "^2.3.6"
Copy link

Copilot AI Mar 20, 2026

Choose a reason for hiding this comment

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

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.

Suggested change
"rdflib": "^2.3.6"
"rdflib": ">=2.3.5 <3.0.0"

Copilot uses AI. Check for mistakes.
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