4.x: Upgrade to MP Config 3.1 and fix an issue with profile specific properties #8757
Conversation
This file contains 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
barchetta
added
MP
config
dependencies
oracle-contributor-agreement
bot
added
the
OCA Verified
tomas-langer
approved these changes
May 29, 2024
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.
Description
ConfigValueeven when value is an unresolved expression (required by new TCK tests)Fixes #8724
Fixes #8738
Documentation
Updated with new MP Config version.
Compatibility
MP Config 3.1 is fully backwards compatible with MP Config 3.0. But the bug fixes in this PR do alter the behavior of our implementation which potentially could impact a small set of users if they were depending on the buggy behavior. For this reason we should do this upgrade in 4.1 instead of 4.0.9.