Conversation
Review Summary by QodoAdd v3 release workflow with validation and publishing
WalkthroughsDescription• Add v3 release workflow triggered manually from vibe3 branch • Validate branch, notify Slack, build and test before release • Generate versions using Lerna with conventional commits • Publish packages to npm with v3 dist-tag Diagramflowchart LR
A["Workflow Dispatch"] --> B["Validate Branch"]
B --> C["Notify Slack"]
B --> D["Build"]
D --> E["Test"]
E --> F["Release"]
F --> G["Generate Versions"]
G --> H["Publish to npm"]
File Changes1. .github/workflows/release-v3.yml
|
Code Review by Qodo
1. Publish is dry-run
|
| - name: Publish to npm with v3 dist-tag | ||
| run: yarn lerna publish from-package --dist-tag v3 --dry-run -y |
There was a problem hiding this comment.
1. Publish is dry-run 🐞 Bug ✓ Correctness
release-v3.yml runs yarn lerna publish ... --dry-run, so no packages are actually published even though the workflow also bumps versions and creates a GitHub release, leaving the repo/releases ahead of npm. This can produce a broken release state where consumers cannot install the released versions.
Agent Prompt
### Issue description
The v3 release workflow does not publish anything because it runs `yarn lerna publish ... --dry-run`, despite creating version bumps/GitHub releases.
### Issue Context
This can create GitHub tags/releases and bumped versions without corresponding npm artifacts.
### Fix Focus Areas
- .github/workflows/release-v3.yml[81-82]
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
CI Feedback 🧐A test triggered by this PR failed. Here is an AI-generated analysis of the failure:
|
https://monday.monday.com/boards/10027056258/pulses/10027056856