-
Notifications
You must be signed in to change notification settings - Fork 0
chore: back-merge v2.4.0 from main to develop #38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
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
- Update version to 2.4.0 in project files - Generate release changelog This commit prepares the release/v2.4.0 branch for release.
- Fix embedded field selector warnings in database package - Complete pagination parameter documentation in all endpoints - Add page parameter support to province cases endpoints - All tests passing and linter clean
- Fix version update script regex patterns to prevent rate limiting value corruption - Update database method calls to use explicit db.DB format for CI compatibility - Regenerate Swagger documentation with corrected rate limiting values
- Add hybrid pagination to /national endpoint (returns all data by default, paginated when parameters provided) - Implement GetNationalCasesPaginated and GetNationalCasesPaginatedSorted service methods - Add GetAllPaginated and GetByDateRangePaginated repository methods with total count - Support limit, offset, and page query parameters with date range filtering - Update Swagger documentation with pagination parameter descriptions - Add pagination methods to all mock interfaces for comprehensive test coverage - Maintain backward compatibility for existing API consumers - Follow consistent pagination pattern matching province endpoints
- Add new job to automatically create PRs to main when release/* or hotfix/* branches are created - Use conventional commit style for PR titles (release: vX.X.X or fix: vX.X.X) - Include deployment checklists and proper labeling - Prevent duplicate PRs with existing PR detection - Support both release and hotfix branch patterns - Clean PR descriptions without attribution text
- Remove duplicate method implementations in covid_service.go - Fix code formatting with gofmt - Update test expectations to match current version 2.4.0 - All tests now passing, build successful
release: v2.4.0
- Update version from 2.4.0 to 2.5.0 in main.go and handlers - Update test expectations to match new version 2.5.0 - Add version management configuration for test files - Fix lint issues in national_case_repository.go (use log.Printf instead of fmt.Printf) - Fix code formatting issues - Regenerate Swagger documentation with version 2.5.0 - All tests passing, build successful
Contributor
Author
🔍 Linting Results🔄 Running full test suite (triggered by critical file changes)
|
Contributor
Author
📊 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 |
Contributor
Author
🎯 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. |
- Remove github.event_name == 'push' condition from create-release job - Job will now run after successful deployment for both push and workflow_dispatch events - Ensures GitHub releases are created consistently after successful deployments
ryanaidilp
approved these changes
Sep 15, 2025
Contributor
Author
📊 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 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Automated back-merge of release v2.4.0 from main to develop branch.
Details
release/v2.4.0chore/back-merge-v2.4.0-to-developWhat this PR does
Auto-generated
This PR was automatically created by GitHub Actions.
Review and merge when ready - this should typically be a straightforward merge unless there are conflicts that need manual resolution.