Add CI build with private dependency mocks - #96
Merged
Conversation
Frotty
marked this pull request as ready for review
August 6, 2026 10:31
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.
What changed
casc-tsandwar3-modelcheckouts in CI with committed API/fixture mocks.Why
The extension consumes
casc-tsandwar3-modelthrough localfile:../...dependencies, but those repositories are not publicly checkoutable in GitHub Actions. The committed mocks preserve the expected sibling layout and enough API/shader/model behavior for CI to validate the extension itself without exposing private sources.Validation
npm run lintnpx tsc -p . --noEmitnpm testnpm testnpm run package-webnpm run test:vsix-contents