Repository navigation
Point the usage-reporting link at a public page - #8
Merged
Merged
Conversation
The old link went to a section of a private repository and 404'd for everyone following it from a program's startup notice. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BZQMN1M5hQKfUpPwDkMjqd
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.
Summary
The usage-reporting "Details" link pointed at a section of the private trace repository, so anyone following it from a program's startup notice got a 404. It now points at the public page https://danielstephenson.dev/usage-reporting.
trace-client.tsdoc comment and the README's startup-notice example use the new URL. The client never prints the URL itself, so no test pins it; programs that copied the README example should update their own notice.[Unreleased]entry describes both changes; earlier entries are untouched.No version bump; the release step is left to the maintainer.
Testing
npm ci && npm run typecheck && npm test: typecheck clean, 0 failures.drafted by Claude on behalf of Daniel Stephenson
🤖 Generated with Claude Code
https://claude.ai/code/session_01BZQMN1M5hQKfUpPwDkMjqd