-
Notifications
You must be signed in to change notification settings - Fork 0
release: v2.3.0 - National pagination support and linter fixes #30
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
Conversation
…improvements fix: resolve linter issues and add national pagination support
- Add pagination parameters (limit, offset, page, all) to national endpoint - Update API documentation to reflect new paginated responses - Include PaginatedResponse model in swagger specs
- Add instruction to always use go expert for this project
- Update version to 2.3.0 in source files - Generate release changelog using generate-changelog.rb - Regenerate API documentation with new version This commit prepares the release/v2.3.0 branch for release.
chore: prepare v2.3.0 release
📊 Code Coverage ReportTotal Coverage: 49.6% Coverage by Package
Detailed CoverageClick to expand detailed coverage
|
🚀 Release Process Completed Successfully The complete Git Flow release process has finished: ✅ Completed Actions
🔄 Deployment PipelineThe deployment workflow is now running and will:
🎉 Git Flow CompleteYour release is now deployed! Monitor the deployment progress and merge the back-merge PR when ready. |
🔄 Back-merge PR Created A back-merge PR has been automatically created to sync the develop branch:
Please review and merge the back-merge PR to complete the release process. |
Release v2.3.0
This release introduces national cases pagination support and resolves various linter issues.
Summary of Changes
New Features
limit
,offset
,page
parametersall=true
parameter for backward compatibilityBug Fixes
API Changes
/national
endpoint now returns paginated responses by default?all=true
to get all data without pagination (backward compatible)Documentation