Repository navigation
chore: update version and changelog - #381
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish 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
[email protected]
Minor Changes
f0a7866: Publish an adapter manifest so server adapters can be driven by data instead of a hand-maintained route list (feat(routes): declare adapter behaviour in defineRoute and emit an adapter manifest #372).
GET /.well-known/seamless-adapter.jsondescribes every route a server adapter exposes: which held token it sends (none,preAuth,registration,access,refresh), which tokens a response issues or clears, which body fields reach the browser under the adapter's cookie transport, and which routes support external message delivery. The same document is committed asadapter-manifest.jsonand regenerated bynpm run generate:api.adapteroption ondefineRoute. Registration fails when a public route does not say whether adapters expose it, when an ephemeral route does not say which token it takes, or when a route that always returns a token does not say what it issues.POST. They send a message, and aGETcan be triggered cross-site without a CORS preflight. TheGETforms still work and are marked deprecated.