Dependency upgrade and 1.6 release changes - #110
Merged
Merged
Conversation
Release 1.6.0 final file changes
🔍 EOL Dependencies Check Results🔍 Dependencies End-of-Life ReportGenerated on 2026-09-28 03:56:51 UTC 📊 Summary
✅ Supported DependenciesClick to expand untracked dependencies
❓ Untracked DependenciesClick to expand untracked dependenciesThese dependencies could not be tracked, as they were not found in the EOL database:
🔧 RecommendationsUseful Resources
|
🧪 Maven Test Results📊 Test Report SummaryTest Results Overview
Module Test Breakdown
This summary was generated by the Maven Test Workflow for Pull Request #110 |
Sonar issue fixes
🔍 EOL Dependencies Check Results🔍 Dependencies End-of-Life ReportGenerated on 2026-09-28 05:43:53 UTC 📊 Summary
✅ Supported DependenciesClick to expand untracked dependencies
❓ Untracked DependenciesClick to expand untracked dependenciesThese dependencies could not be tracked, as they were not found in the EOL database:
🔧 RecommendationsUseful Resources
|
🧪 Maven Test Results📊 Test Report SummaryTest Results Overview
Module Test Breakdown
This summary was generated by the Maven Test Workflow for Pull Request #110 |
|
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
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.
Please refer to our contributing docs for any questions on submitting a pull request.
Issues are required for both bug fixes and features.
Resolves #ISSUE_NUMBER
Describe behaviour before the change
Prior to this release, the application had older dependency versions and lacked several user attribute management and client filtering capabilities. The system supported basic user attribute operations but did not have comprehensive endpoints for managing additional attribute definitions and values, nor did it support advanced client search and filtering with pagination.
Describe behaviour after the change
Release 1.6.0 introduces significant enhancements:
Dependency Upgrades:
New API Endpoints for User Attributes:
/users/attributes/additional- Retrieve all additional attribute definitions/users/attributes/{attributeName}- Delete an attribute definition/users/{id}/attributes/values- Get a user's additional attribute values/users/{id}/attributes/values- Add/modify a user's additional attribute values/users/{id}/attributes/values/{attributeName}- Delete a specific user's attribute valueNew Client Filtering API:
/oauth2/client/filter- Advanced client search with pagination, sorting, and multiple filter criteria (client IDs, names, statuses)Code Quality & Compatibility Improvements:
ClientFilterDtoDTO for client filter request validation with constraint annotationsClientFilterResponseDTO for paginated client responsesClientSearchSpecificationfor dynamic client search using JPA SpecificationsClientStatusenum with JSON serialization support (@JsonCreator,@JsonValue)GlobalExceptionHandlerto use JPA's genericPathinstead of removed HibernatePathImplIgniteLoggerImplcompatible with Logback 1.6 (replaces removedPatternLayout.defaultConverterMap)logback-spring.xmlconfiguration for Logback 1.6 compatibilityexistsByAttributeId()to check attribute value referencesUsersServiceImplwith complete CRUD operations for user attribute valuesPull request checklist
Does this introduce a breaking change?
Note: While dependency versions are upgraded, backward compatibility is maintained. The new APIs are additive and do not break existing functionality.