fix: resolve pipeline crashes in existing CI workflow and fix TS6059#18
Merged
Lakes41 merged 9 commits intoJun 13, 2026
Merged
Conversation
…otocol definitions
…ative npm compatibility
… and include docs build
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
2 participants
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.
Description
While addressing the missing CI validation issue, I discovered an existing
ci.ymlthat was actively failing due to two structural issues:npm ciwas throwingEUNSUPPORTEDPROTOCOLdue to theworkspace:*syntax in the package.json files.npm run typecheckwas failing due to aTS6059configuration error in thediscord-botworkspace.This PR merges the intended CI steps with the necessary patches to actually get the pipeline to pass.
closes #12
Changes Made
sedpatch step to dynamically convertworkspace:*to*for the runner.npm citonpm installto allow native workspace linking.apps/discord-bot/tsconfig.jsonto resolve the rootDir include conflict.npm run build:docscommand to the pipeline.