Repository navigation
v1.4.0 - #29
Merged
Merged
v1.4.0#29
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Moves js-yaml, brace-expansion and source-map-js to their patched releases. Dev-only; the published package is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Release PR: bumps the package version to 1.4.0 and promotes the Unreleased work (Tango API 5.1.0 through 5.11.0 parity with tango-python: Federal Register documents, GSA eBuy requests, contract appeals, SLED procurement,
obligations_by_fiscal_year,PaginatedResponse.countType, and more) to the dated 1.4.0 changelog section. Minor bump: new features and fixes, no breaking changes.A second commit runs
npm audit fix(no--force) on dev dependencies, moving js-yaml, brace-expansion and source-map-js to patched releases. The vitest / @vitest/mocker advisory is not resolved bynpm audit fixand is left for a follow-up. The published package is unaffected.After merge, publishing a GitHub Release tagged v1.4.0 triggers the npm publish workflow.
Local gates: lint, typecheck, build, 562 tests, filter/shape conformance against the vendored contract, shape coverage,
npm pack --dry-run.🤖 Generated with Claude Code