Repository navigation
Standardize release checks with fast check and E2E - #324
Merged
Merged
Conversation
commit: |
ianmacartney
changed the title
ianmacartney
changed the title
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.
The shared release workflow runs
npm run build, fastnpm run check, then requirednpm run test:e2e. The E2E command generates component code; the clean CI checkout verifies tracked and untracked generated files before packing. Workflow's PR CI runs fast checks before resolving the backend and running E2E. Its existing E2E wrapper accepts the cached backend version throughBACKEND_VERSION.checkremains usable without network access or environment variables during development. Verified locally: 129 unit tests, typecheck, lint, formatting, E2E, and generated-file verification passed.Related migration: convex/migrations#81