v7.0.5

Fixed issues:

• Prevent error when switching accounts #1845
• Add priorities to RDF types when converting #1868
• Allow path segments to start with 2 or more dots #1874

See the CHANGELOG for all changes.

v7.0.4

This release replaces all rdf-js imports with @rdfjs/types. This is only relevant if you have a project that depends on this one and has no impact on running the server as-is.

See the CHANGELOG for all changes.

v7.0.3

Fixed issues:

• Require Append instead of Write permissions when creating a new resource with PUT #1825
• Fixed an issue when linking external WebIDs to your account #1827
• Better defaults when starting the server through code #1811

See the CHANGELOG for all changes.

v7.0.2

Fixed issues:

• Prevent storage issues with invalid JSON resources
• Prevent cached files from causing problems on account pages
• Return correct content-length header when combining the server with a user interface
• Prevent submit buttons on account pages from being clicked before data is loaded

See the CHANGELOG for all changes.

v7.0.1

Fixed issues:

• The configuration option to disable account management resulted in errors.
• The npm release had the wrong capitalization for some files resulting in errors on certain file systems.

v7.0.0

See the RELEASE NOTES for an overview of the major changes and the impact on the configurations.

The main new feature of this release is the updated account management. Everything related to account management has been drastically changed. Some of the new possibilities with accounts:

• One account can have multiple pods.
• The owners of a pod can be updated.
• One account can register multiple WebIDs. When authenticating with a Solid app you choose which WebID to identify as.
• One account can have multiple email/passwords to log in with. Passwords can also be updated.
• Client credentials tokens can be created through the interface.
• The architecture has been refactored so that it should be more easy to introduce new login methods.

The configuration generator has been updated with the new configuration options available.

In case you want to upgrade an existing v6 server, internal data will be migrated the first time the server is started after the update. Make sure to read the details of what migration does in the RELEASE NOTES.

See the CHANGELOG for all changes.

v6.1.0

Release version 6.1.0 of the npm package. See the CHANGELOG for details.

• Adds support for the HTTP Range header.
• Fixes an issue where expired data on long-running servers was not always cleaned up.

v6.0.2

Release version 6.0.1 of the npm package. Contains various minor fixes. See the CHANGELOG for details.

v6.0.1

Release version 6.0.1 of the npm package. Contains various minor fixes.

What's Changed

• Use correct type for Webhook notifications (c0a881b)
• Make root storage subject of storage description (9584ab7)
• Prevent illegal file paths from being generated (fdee4b3)

v6.0.0

Release version 6.0.0 of the npm package.

This releases comes with several major changes, including:

• ACP can be used instead of WAC for authorization if preferred.
• Support for v0.2 of the new notification specification. This includes support for both WebSocket and WebHook notifications.

To help customize an instance of the server suited to your needs, there is now also a configuration tool that generates configurations.

See the RELEASE NOTES for an overview of the major changes and the impact on the configurations.

See the CHANGELOG for all changes.