Releases: fedify-dev/fedify
Fedify 1.1.4
Released on November 12, 2024.
-
Fixed a bug where default document loaders had thrown a
TypeErrorwith a messageBody is unusable: Body has already been read
orBody already consumed
when the content type of the response was an HTML document and there's no link to a JSON-LD document. -
Fixed a bug where
verifySignature()andverifyJsonLd()functions sometimes had thrown ajsonld.ValidationErrorerror. Now such errors are caught and logged as warnings, and the signature to verify is considered as invalid.
Fedify 1.0.8
Released on November 12, 2024.
-
Fixed a bug where default document loaders had thrown a
TypeErrorwith a messageBody is unusable: Body has already been read
orBody already consumed
when the content type of the response was an HTML document and there's no link to a JSON-LD document. -
Fixed a bug where
verifySignature()andverifyJsonLd()functions sometimes had thrown ajsonld.ValidationErrorerror. Now such errors are caught and logged as warnings, and the signature to verify is considered as invalid.
Fedify 0.15.6
Released on November 12, 2024.
- Fixed a bug where default document loaders had thrown a
TypeErrorwith a messageBody is unusable: Body has already been read
orBody already consumed
when the content type of the response was an HTML document and there's no link to a JSON-LD document.
Fedify 1.2.3
Released on November 6, 2024.
- The
fedify nodesubcommand now can recognize multiple values of therelattribute in the<link>HTML elements.
Fedify 1.2.2
Released on November 1, 2024.
-
Handle connection errors (rather than HTTP errors) in the
Context.sendActivity()method. -
Support the
fedifycommand on Windows on ARM64 via x64 emulation. [#160]
Fedify 1.2.1
Released on October 31, 2024.
- Now
fedify nodecommand can render the node's favicon withimage/vnd.microsoft.iconorimage/x-iconformat.
Fedify 1.2.0
Released on October 31, 2024.
-
Added
InboxContext.recipientproperty. -
Added NodeInfo client functions.
- Added
getNodeInfo()function. - Added
GetNodeInfoOptionsinterface. - Added
parseNodeInfo()function. - Added
ParseNodeInfoOptionsinterface.
- Added
-
Re-exported Semantic Versioning-related types and functions:
- Added
SemVertype. - Added
formatSemVer()function. - Added
parseSemVer()function.
- Added
-
Added
followedMessageproperty toActortype in Activity Vocabulary API.- Added
Application.followedMessageproperty. new Application()constructor now acceptsfollowedMessageoption.Application.clone()method now acceptsfollowedMessageoption.- Added
Group.followedMessageproperty. new Group()constructor now acceptsfollowedMessageoption.Group.clone()method now acceptsfollowedMessageoption.- Added
Organization.followedMessageproperty. new Organization()constructor now acceptsfollowedMessageoption.Organization.clone()method now acceptsfollowedMessageoption.- Added
Person.followedMessageproperty. new Person()constructor now acceptsfollowedMessageoption.Person.clone()method now acceptsfollowedMessageoption.- Added
Service.followedMessageproperty. new Service()constructor now acceptsfollowedMessageoption.Service.clone()method now acceptsfollowedMessageoption.
- Added
-
Log messages now can be traced using LogTape's implicit contexts. [#118]
-
Added options for an AMQP driver to
fedify initcommand.- Added
amqpvalue to the-q/--message-queueoption of thefedify initcommand.
- Added
-
Added
fedify nodesubcommand. -
Added more log messages using the LogTape library. Currently the below logger categories are used:
["fedify", "nodeinfo", "client"]
Fedify 1.1.3
Released on October 31, 2024.
- Fixed a bug where
fetchDocumentLoader()function had disallowed redirecting to a private network address when the second parameter, abooleanvalue to allow private network addresses, wastrue.
Fedify 1.0.7
Released on October 31, 2024.
- Fixed a bug where
fetchDocumentLoader()function had disallowed redirecting to a private network address when the second parameter, abooleanvalue to allow private network addresses, wastrue.
Fedify 0.15.5
Released on October 30, 2024.
- Fixed a bug where
fetchDocumentLoader()function had disallowed redirecting to a private network address when the second parameter, abooleanvalue to allow private network addresses, wastrue.