fedify 2.1.6 - #278421
Merged
Merged
Conversation
daeho-ro
approved these changes
Apr 20, 2026
Contributor
|
馃 An automated task has requested bottles to be published to this PR. Caution Please do not push to this PR branch before the bottle commits have been pushed, as this results in a state that is difficult to recover from. If you need to resolve a merge conflict, please use a merge commit. Do not force-push to this PR branch. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Created by
brew bumpCreated with
brew bump-formula-pr.release notes
@fedify/astroby making the build emit dist/*.js and dist/*.d.ts files that match the published package metadata again. This fixes package resolution failures caused by package.json exporting files that did not exist in the npm tarball. [#699, #701]@fedify/cli
fedify lookupfailing to look up URLs on private or localhost addresses unless-p/--allow-private-addresswas passed, which was a regression introduced in Fedify 2.1.0 when the CLI began forwarding theallowPrivateAddressoption to the underlying document loader. URLs explicitly provided on the command line now always allow private addresses, while URLs discovered during-t/--traversehonor the option to mitigate SSRF attacks against private addresses. Recursive fetches via--recursecontinue to always disallow private addresses regardless of the option. [#696, #698 by Chanhaeng Lee]View the full release notes at https://github.com/fedify-dev/fedify/releases/tag/2.1.6.