docs: the per-call settings validation gap is fixed in the current artifact build - #457
Merged
Merged
Conversation
…tifact build The artifact producer's build 20261004.021416, which every tag now resolves to, refuses an invalid per-call setting value with the server's own code and refuses a filter created with an invalid session_timezone (36). The first 1.0 build stays fetchable by digest or through a lock, so the entry keeps its workaround for that build and says how to move to the current one. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012NdkF6p8Q3qkdxKCgbdjgb
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.
docs: the per-call settings validation gap is fixed in the current artifact build. The artifact producer's build
20261004.021416(now the default for every tag) refuses an invalid per-call setting value with the server's own code, and refuses a filter created with an invalidsession_timezone(36). The entry indocs/limitations.md#known-gaps-in-10now says so. It keeps the workaround for the first 1.0 build, which stays fetchable by digest or lock. Docs only.🤖 Generated with Claude Code
https://claude.ai/code/session_012NdkF6p8Q3qkdxKCgbdjgb