chore: bump version to v2.5.0 for next development cycle #36
Conversation
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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=80&v=4){kind=small}
Following release branch creation for v2.4.0, updating develop branch to target the next minor version v2.5.0. Changes: - Update project version to 2.5.0 - Prepare for next development cycle This maintains the Git Flow pattern where develop always contains the next planned version.
🔍 Linting Results🔄 Running full test suite (triggered by critical file changes)
|
🎯 CI Pipeline Summary🔄 Running full test suite (triggered by critical file changes) 📊 Job Status
🎉 Overall Result: SUCCESSAll CI checks completed successfully! The code is ready for review/merge. |
- Add page parameter to pagination-enabled endpoints
- Regenerate Swagger docs with complete pagination support
- Fix /provinces/cases and /provinces/{provinceId}/cases endpoints
- All pagination endpoints now include limit, offset, page, and all parameters
- Fix database embedded field selector issues for linter compliance - Update mock interfaces to include new pagination methods - Fix version assertions in tests from 2.4.0 to 2.5.0 - All tests and linting now pass successfully
ryanaidilp
approved these changes
Sep 15, 2025
📊 Enhanced Code Coverage Report🔄 Running full test suite (triggered by critical file changes) 🎯 Coverage Summary
📦 Package Coverage Analysis
🔍 Testing Strategy Applied
💡 RecommendationsPackages needing attention:
📋 Detailed CoverageClick to expand detailed coverage by file |
- Fix version script bug that replaced rate limiting "100" with "2.5.0" - Remove formatting artifacts (\t\t) from API description - Regenerate Swagger docs with correct "100 requests per minute" value - Maintain proper API documentation consistency
📊 Enhanced Code Coverage Report🔄 Running full test suite (triggered by critical file changes) 🎯 Coverage Summary
📦 Package Coverage Analysis
🔍 Testing Strategy Applied
💡 RecommendationsPackages needing attention:
📋 Detailed CoverageClick to expand detailed coverage by file |
- Revert database method calls to use db.DB.MethodName() format - Fix typecheck linter errors in CI pipeline - Local staticcheck warnings acceptable vs CI build failures - All tests continue to pass with explicit field access
📊 Enhanced Code Coverage Report🔄 Running full test suite (triggered by critical file changes) 🎯 Coverage Summary
📦 Package Coverage Analysis
🔍 Testing Strategy Applied
💡 RecommendationsPackages needing attention:
📋 Detailed CoverageClick to expand detailed coverage by file |
ryanaidilp
approved these changes
Sep 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
Automatic version bump following release branch creation.
Details
release/v2.4.0Changes Made
Git Flow Pattern
This maintains the Git Flow pattern where:
developalways contains the next planned versionAuto-generated
This PR was automatically created when the release branch was created.
Safe to merge - contains only version bumps.