Repository navigation
Lean serverInfo output by default and CI action updates - #43
Merged
Merged
Conversation
The default response now contains version, storage engines, BSON limits and connection info only. Large build environment details (compiler flags) and server status moved behind includeDebugInfo, cutting the default payload from ~3.7k to ~300 characters.
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
Two small maintenance improvements.
Lean
serverInfooutputThe default
serverInforesponse previously included the fullbuildEnvironmentblock (compiler and linker flags), consuming thousands of tokens per call while providing no value to LLM agents. The response now contains only the essentials —version,gitVersion,storageEngines,maxBsonObjectSize,bits,okandconnectionInfo— cutting the default payload from ~3.7k to ~300 characters.Verbose details (
buildEnvironment,openssl,allocator,modulesand the fullserverStatusblock) are still available when explicitly requested viaincludeDebugInfo: true.CI
Updated
actions/checkoutandactions/setup-nodefrom v4 to v5 in both publish workflows, resolving the Node 20 deprecation warnings emitted during the 2.1.0 release run.Testing
includeDebugInfo: truereturns the full payload includingbuildEnvironmentandserverStatus.