Repository navigation
Release 2.0.0 with nested result metadata - #11
Merged
Merged
Conversation
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.
The HTTP API moves GitHub/Hacker News fields into optional per-result
metadata. Update public result types, documentation, and regression coverage to use the new paths, with no top-level compatibility aliases. Keeppublished_dateat the top level.Prepare version 2.0.0 for this breaking response correction. Update the bundled agent skill and add PR CI so checks run before merging. Validation: 28 tests and TypeScript build.
PR CI also exposed a reproducible Node 18 repeated-login failure: the second OAuth authorization reused a keep-alive connection to the retired callback server. Set
Connection: closeon one-shot callback responses, assert it in the existing end-to-end test, and verify all 28 tests on Node 18 and 22.