chore: back-merge v2.3.0 from main to develop #31
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}
…improvements fix: resolve linter issues and add national pagination support
…filtering-improvements Revert "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
release: v2.3.0 - National pagination support and linter fixes
ryanaidilp
approved these changes
Sep 8, 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
Automated back-merge of release v2.3.0 from main to develop branch.
Details
release/v2.3.0chore/back-merge-v2.3.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.