ci(release): avoid building benchmarks on publish#1664
ci(release): avoid building benchmarks on publish#1664colinaaa merged 1 commit intolynx-family:mainfrom
Conversation
|
📝 WalkthroughWalkthroughThe deploy-main GitHub Actions workflow updates the Turbo build filters in the publish job to additionally exclude benchx_cli and packages matching @lynx-js/benchmark-*. No other steps or logic are changed; canary publish remains unchanged. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Possibly related PRs
Suggested reviewers
Poem
✨ Finishing Touches🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (3)
.github/workflows/deploy-main.yml (3)
50-52: Quote all negation filters for shell-safety and consistency.Minor: quote the
!filters here as well.- corepack pnpm turbo --filter !@lynx-js/web-tests --filter !benchx_cli --filter "!@lynx-js/benchmark-*" build --summarize + corepack pnpm turbo --filter "!@lynx-js/web-tests" --filter "!benchx_cli" --filter "!@lynx-js/benchmark-*" build --summarize
139-141: Use $GITHUB_OUTPUT instead of deprecated set-output.GitHub deprecated
::set-output::.- - name: Get current date - id: date - run: echo "::set-output name=date::$(date -u +'%Y-%m-%d %H:%M:%S')" + - name: Get current date + id: date + run: echo "date=$(date -u +'%Y-%m-%d %H:%M:%S')" >> "$GITHUB_OUTPUT"
185-186: Consider excluding benchmarks in canary build too (time saver).If canary doesn’t need benchmarks, mirror the publish filters.
- corepack pnpm turbo --filter !@lynx-js/web-tests build --summarize + corepack pnpm turbo --filter "!@lynx-js/web-tests" --filter "!benchx_cli" --filter "!@lynx-js/benchmark-*" build --summarize
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
.github/workflows/deploy-main.yml(1 hunks)
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: 2025-08-25T09:16:24.277Z
Learnt from: CR
PR: lynx-family/lynx-stack#0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-08-25T09:16:24.277Z
Learning: Always run a full build with `pnpm turbo build` before running any tests
Applied to files:
.github/workflows/deploy-main.yml
🔇 Additional comments (1)
.github/workflows/deploy-main.yml (1)
137-138: Fix Turbo flag order: filters must precede the task.Placing
--filterafterbuildmay be ignored; this can still build benchmarks during publish.Apply:
- corepack pnpm turbo --filter !@lynx-js/web-tests build --filter !benchx_cli --filter "!@lynx-js/benchmark-*" --summarize + corepack pnpm turbo --filter "!@lynx-js/web-tests" --filter "!benchx_cli" --filter "!@lynx-js/benchmark-*" build --summarize⛔ Skipped due to learnings
Learnt from: CR PR: lynx-family/lynx-stack#0 File: .github/copilot-instructions.md:0-0 Timestamp: 2025-08-25T09:16:24.277Z Learning: Always run a full build with `pnpm turbo build` before running any tests
React Example#4875 Bundle Size — 238.02KiB (0%).1f59678(current) vs 79d7030 main#4874(baseline) Bundle metrics
|
| Current #4875 |
Baseline #4874 |
|
|---|---|---|
0B |
0B |
|
0B |
0B |
|
0% |
0% |
|
0 |
0 |
|
4 |
4 |
|
160 |
160 |
|
65 |
65 |
|
45.84% |
45.84% |
|
2 |
2 |
|
0 |
0 |
Bundle size by type no changes
| Current #4875 |
Baseline #4874 |
|
|---|---|---|
145.76KiB |
145.76KiB |
|
92.26KiB |
92.26KiB |
Bundle analysis report Branch colinaaa:colin/0908/release Project dashboard
Generated by RelativeCI Documentation Report issue
Web Explorer#4866 Bundle Size — 367.43KiB (0%).1f59678(current) vs 79d7030 main#4865(baseline) Bundle metrics
Bundle size by type
|
| Current #4866 |
Baseline #4865 |
|
|---|---|---|
235.43KiB |
235.43KiB |
|
100.16KiB |
100.16KiB |
|
31.84KiB |
31.84KiB |
Bundle analysis report Branch colinaaa:colin/0908/release Project dashboard
Generated by RelativeCI Documentation Report issue
CodSpeed Performance ReportMerging #1664 will improve performances by 12.82%Comparing Summary
Benchmarks breakdown
|
Following up #1629.
Summary by CodeRabbit
Checklist