[codex] Keep SDK release metadata and toolchain current#9
Merged
Conversation
The public SDK repo lagged the published npm package and still carried stale dev-tool transitive locks. This syncs the package version to 2.1.1, refreshes the TypeScript/Vitest/tsup/YAML toolchain, pins patched esbuild/Rollup transitive versions through npm overrides, and makes the compiler config explicit for Node 18 plus fetch/Abort globals.\n\nConstraint: @vertaaux/sdk@2.1.1 is already the npm latest and the repo should reproduce that release state.\nConstraint: tsup 8.5.1 still allows vulnerable esbuild/Rollup ranges, so overrides are required until upstream narrows them.\nRejected: Downgrade tsup to npm audit's suggested 6.5.0 | that would roll back the build toolchain to avoid transitive advisories instead of keeping current patched dependencies.\nConfidence: high\nScope-risk: moderate\nDirective: Remove the esbuild/Rollup overrides only after tsup depends on patched ranges itself and npm audit remains clean.\nTested: npm run typecheck; npm test; npm run build; npm audit --audit-level=moderate; npm pack --dry-run --json\nNot-tested: Publishing to npm
This was referenced Jun 17, 2026
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
Why
The repo main branch lagged the already-published npm package and still carried stale transitive locks behind the open dependency PRs. This consolidates the dependency cleanup into one branch.
Verification
Follow-up after merge