ci: add project regression checks#494
Closed
JustYannicc wants to merge 1 commit into
Closed
Conversation
Collaborator
Author
|
Superseded by #532 (fix(validation): restore project checks), which consolidates this validation/build change with the related source PRs. Closing this PR in favor of the upstream replacement. |
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
Added a lightweight root
Project ChecksGitHub Actions workflow for pull requests, pushes tomain, and manual runs.The workflow runs on Node 22 with npm caching and covers:
npm testnpm run check:i18nnpm run build:mainnpm run build:rendererIt installs dependencies with native postinstall scripts disabled and skips the live Electron harness on Ubuntu so the job stays focused on fast regression coverage rather than macOS packaging.
Why
The current workflows cover Claude review/assistant flows and the canvas bundle, but do not run the normal root project test/i18n/build checks. That leaves performance cleanup PRs vulnerable to quiet regressions in ranking tests, i18n structure, main-process TypeScript compilation, or renderer bundling.
Compatibility impact
CI-only change. No runtime code, packaged app behavior, or Raycast extension API surface changes.
How tested
/opt/homebrew/Cellar/node@22/22.22.3/bin/npm ci --ignore-scripts --forceSUPERCMD_SKIP_ELECTRON_TESTS=1 /opt/homebrew/Cellar/node@22/22.22.3/bin/npm test- 25 tests reported, 24 pass, 1 Electron live test skipped/opt/homebrew/Cellar/node@22/22.22.3/bin/npm run check:i18n- exits 0; existing non-strict Italian gaps still warn/opt/homebrew/Cellar/node@22/22.22.3/bin/npm run build:main/opt/homebrew/Cellar/node@22/22.22.3/bin/npm run build:rendererjs-yamlvite.config.tsreported no errors; YAML LSP could not run in this local environment because its installedyaml-language-serverpackage is missingvscode-languageserver-protocolRisks
npm ci --forceis intentional becausepackage.jsonpins darwin esbuild platform packages for release packaging; without it, npm rejects the lockfile on a single runner platform.check:i18ncurrently treats only configured strict locales as failures, so non-strict locale drift remains a warning unless that script policy changes later.