Repository navigation
chore(ci): fix prepack scripts - #39
Conversation
|
No actionable comments were generated in the recent review.
|
| Layer / File(s) | Summary |
|---|---|
Remove the script setting pnpm-workspace.yaml |
The workspace configuration no longer sets ignoreScripts: true. |
Priority:
Estimated code review effort: 1 (Trivial) | ~5 minutes
Change: Bug fix
Merge Risk: 
Minimal · up to 799e9
-
The configuration now permits the package builds to run during release packing. No merge-blocking issue was identified.
Pre-merge checks: 
5
-
Full details: Docstring Coverage
-
Explanation
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files.
Full details: Description check
-
Explanation
The description explains the change and identifies the release workflow problem caused by ignoreScripts: true. The Linked Issues and Additional Context sections are empty, but no linked issue or extra reviewer focus is required to understand the change.
-
Finishing Touches
-
🧪 Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
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 @coderabbitai help to get the list of available commands.
commit: |
Description
This PR removes
ignoreScripts: truefrom pnpm workspace (we also have allowBuilds):ignoreScripts: truebreaks the release workflow when running pack, prepack script won't run (that runs the tsdown build) and so package tgz files empty.Linked Issues
Additional Context
Summary by CodeRabbit