Repository navigation
fix(build): vendor ragent-oss SDK to restore clean builds - #78
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
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.
Problem and change
A clean frontend build fails with npm 404 because
ragent-oss@0.1.0was unpublished. Vendor the recovered installed SDK undervendor/ragent-ossand resolve it through a localfile:dependency, so builds no longer download this package from npm.The Docker builder copies the SDK before dependency installation. Existing imports, Next.js transpilation, and the OSS gateway protocol are preserved. The lockfile changes only the SDK resolution; package provenance and per-file SHA-256 checksums are included. This contains the client SDK, not the storage gateway server.
Validation
pnpm install --frozen-lockfilewith pnpm 11.20.0: passed.git diff --check: passed.Execution checks were performed in the private frontend verification checkout. The public patch's 12 changed files are byte-identical to that tested version, and the six relevant baseline configuration files match. Public patch applicability and file equality were checked separately. The existing Next.js configuration skips type and lint validation; live OSS calls were not exercised.
Private production synchronization follows this public PR's merge.