chore: version packages - #165
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 6, 2026 19:41
a637146 to
0eb2286
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
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
@taujs/mcp@0.9.0
Minor Changes
#166
b4bc618Thanks @aoede3! -@taujs/mcpreads the observations schema-version-2 additions from@taujs/server(RFC 0018).taujs_who_calls_servicegains ahostObservedlist: a Fastify route the application registered itself, seen calling the registry in development traffic, reported separately fromdeclaredandobservedso it is never mistaken for a declared edge.taujs_explain_routecan now answer for such a path from episodes rather than refusing outright, and its wording for a path with no episodes says "no observation", never that no request occurred.Reading
episodes.ndjsonis now gated as a paired read withobservations.json's schema version: both refuse together on a mismatch, fail closed, rather than reading episode records individually.@taujs/server@0.39.0
Minor Changes
#166
b4bc618Thanks @aoede3! - Host-route attribution (RFC 0018): in development, τjs observes registry-backed work performed through ordinary Fastify route handlers, without taking ownership of those routes. When a handler outside τjs's own routes calls the service registry throughcallServiceMethodwith no explicit recorder, the call is correlated to a host-observed episode carrying the route's method and path, the registry calls made in it, and the response outcome - opened only once the registry is called, and never touching the route, its transport or its error handling.EpisodeRecorder.routeMatchedgains a requiredkind: 'page' | 'host'and an optionalmethod;appIdandrenderbecome optional, since a host route has neither.sentis discriminated bykind, andfailednow carries the responsestatusalongside its optionalerror. The observations schema moves to version 2 for these additions.Nothing changes for an application that never calls a Fastify route outside τjs's own: page episodes, their identities and
observations.json's edge shapes are unaffected beyond the schema-version bump. Production behaviour is unchanged - nothing binds unless introspection is already active in development.playground-react@0.0.55
Patch Changes
b4bc618]:rfc-0014-recipe@0.0.14
Patch Changes
b4bc618]: