Merged
Conversation
…tag creation to remove 'v' prefix from version strings. Update documentation to reflect changes in tag creation process and clarify version formatting.
…sts to include 'v' prefix for consistency
|
To view this pull requests documentation preview, visit the following URL: Documentation is deployed and generated using docs.page. |
Closed
1 task
vypbot
added
the
size: XL
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #325 +/- ##
===========================================
- Coverage 90.86% 90.86% -0.01%
===========================================
Files 135 135
Lines 6198 6215 +17
Branches 1329 1333 +4
===========================================
+ Hits 5632 5647 +15
- Misses 171 172 +1
- Partials 395 396 +1
🚀 New features to boost your workflow:
|
Contributor
🐛 Bugfix Actions
Debug log🚀 Happy coding! Made with ❤️ by vypdev/copilot |
…eUseCase for empty changelog scenarios
…eUseCase for empty title scenarios
vypbot
reviewed
Mar 10, 2026
| @@ -42,6 +42,7 @@ export class CreateReleaseUseCase implements ParamUseCase<Execution, Result[]> | |||
| ], | |||
Contributor
There was a problem hiding this comment.
Potential release version format not validated
Severity: medium
Location: src/usecase/actions/create_release_use_case.ts
CreateReleaseUseCase validates that version, title, and changelog are non-empty, but there is no validation of the actual format of the version string before constructing the release tag (prefixing with 'v'). If an invalid version is supplied (e.g., non-numeric, includes a leading 'v'), the generated release tag may be malformed (e.g., 'vv1.2.3').
Suggested fix:
Validate the version string against a semantic version pattern (e.g., /^(\d+)(?:.(\d+)){0,2}$|^\d+.\d+.\d+$/) or use a semver library, and ensure the 'v' prefix is applied consistently only after validation.
Written by vypdev/copilot for commit a52be8edfc225ef2e69259e13b5576198f9ab65d. This will update automatically on new commits.
…easeUseCase to ensure semantic versioning compliance and enhance error handling for invalid versions.
Contributor
🐛 Bugfix Actions
Debug log🚀 Happy coding! Made with ❤️ by vypdev/copilot |
This was referenced Mar 10, 2026
Closed
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
3 participants
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.
Summary
Fix release tag generation to use the correct source branch and consistent naming. Tags are now created from release/2.0.4 (not from master) and follow a single, prefixed naming convention (e.g., v.2.0.4). This prevents creation of unintended tags such as 2.0.4 and ensures only one tag is produced per release.
Related Issues
Scope of Changes
Technical Details
How to Test
Test Coverage / Deployment / Security / Performance / Checklist
Breaking Changes
None. This is an automation fix for release tagging and does not alter runtime code or public APIs.
Notes for Reviewers / Additional Context