chore(release): 0.8.1 - #18
Merged
Merged
Conversation
Ships the request-path redaction from #17: on a matched route the span carries the route template, not the customer's concrete file path. README documents the behaviour under 'What gets traced'. Also exports readableRoute, which un-mangles express RegExp routes from their regex source.
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.
Releases the request-path redaction from #17, which is merged but unpublished - the publish gate fires on a
chore(release)commit touchingpackage.json, and #17 carried no bump.Patch rather than minor, matching this repo's convention (0.7.1 shipped a new
setSpanAttributesexport). It does add one export,readableRoute.After this publishes
The kit only redacts once services consume it.
web(memory-mcp, backend, sync) is where the content routes live, so it wants the bump first; landing, catalog, dashboard and admin pick up the readable-route improvement whenever they next bump.npm run verifygreen, 81/81.