Prepare next release - #50
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
August 19, 2026 17:20
8e9eef0 to
f3d98a0
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 15, 2026 16:53
f3d98a0 to
941ba0e
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 15, 2026 17:26
941ba0e to
cc5a7d2
Compare
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
1 participant
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@germ-network/atprotoclient@0.9.0
Minor Changes
c9d149eThanks @germ-mark! - AddAtproto.DidWebResolver: resolves a did:web identifier to its DID document by fetchinghttps://{host}/.well-known/did.json, matching@atproto/identity's reference resolver (Accept header, redirect refusal, single-segment restriction). Screens the resolved host against a strict hostname allowlist before ever fetching, since a did:web identifier is attacker-influenced input turned directly into a URL (Linear GER-1912) — no port, loopback, or IP-literal host is accepted. Defaults to a redirect-refusing session; fetcher injection is reserved for tests.Patch Changes
#53
5d1ea0aThanks @germ-mark! - Fix build against GermConvenience 0.8.0, which splitHTTPDataResponseandHTTPFetcherout of the baseGermConveniencelibrary into a newGermConvenienceHTTPproduct. Adds theGermConvenienceHTTPproductdependency and the matching import everywhere those types are used, and
raises the floor to
from: "0.8.0".No public API change — this only restores buildability against current
GermConvenience releases.