Repository navigation
fix(ci): hardcoded v3 prefix in version and release workflows - #1008
Conversation
version.yml used prefix=3 for main branch, prefix=4 for dev. release.yml hotfix path generated v3.YYMMDD.N instead of v4. This caused v3.260403.1 to be created on top of v4.260402.18 when a direct merge to main triggered the release workflow. All three v3 references updated to v4: - version.yml: main branch prefix 3 → 4 - release.yml: hotfix version prefix 3 → 4 - release.yml: fallback release notes "v3" → "v4"
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe GitHub Actions workflows are updated to switch version tagging from v3 to v4 format. The release workflow's hotfix logic now targets v4.. tags and updates the default release notes. The version workflow hardcodes the version prefix to 4 instead of conditionally selecting it based on the branch. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Possibly related PRs
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
version.yml used prefix=3 for main branch, prefix=4 for dev. release.yml hotfix path generated v3.YYMMDD.N instead of v4.
This caused v3.260403.1 to be created on top of v4.260402.18 when a direct merge to main triggered the release workflow.
All three v3 references updated to v4:
Summary by CodeRabbit