Release - #28
Merged
Merged
Release#28
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Collaborator
|
@greptileai review |
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 24, 2026 08:59
93f8d01 to
ebd5110
Compare
|
Collaborator
|
@greptileai review |
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
@hypercerts/hypercerts-feed-service@0.2.0
Minor Changes
#22
0c8b281Thanks @Kzoeps! - Feed requests can now use AT Protocol service authentication. If a request includes a valid token, the token's issuer becomes the feed viewer. Requests without a token still needparams.viewerDid. Authenticated tokens must include a non-emptyjtiof no more than 256 UTF-8 bytes and can be used only once per running process; retries require a fresh token, including after downstream failures.Replay protection allows up to 512 live entries per verified issuer and 4,096 live entries per process. It is not shared across replicas or restarts. A full live issuer quota or replay store returns HTTP 503 until entries expire, preserving capacity for other issuers until the global bound is reached.
Before upgrading, set
SERVICE_DIDto this service's DID, even if you do not use authentication. It must be a bare DID, without#serviceId. If it is a hostname-leveldid:weband the matching hostname points to this service,GET /.well-known/did.jsonnow publishes a#hypercerts_feedservice entry at that hostname for discovery.Node HTTP requests now retain working service authentication after their POST body finishes. The service upgrades
@atproto/lex-serverto 0.1.19 and avoids passing its prematurely aborted request signal to DID resolution. Thedid#serviceIdformat from AT Protocol Proposal 0014 is not supported yet because@atproto/lex-serverdoes not support it.