Update dependency space.arim.dazzleconf:dazzleconf-ext-snakeyaml to v1.3.0-RC1 #23
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.
This PR contains the following updates:
1.3.0-M1→1.3.0-RC1Release Notes
A248/DazzleConf (space.arim.dazzleconf:dazzleconf-ext-snakeyaml)
v1.3.0-RC1: : Capitalizing on maturity while preparing for version 2.0Compare Source
This series, 1.3.0, will be the last DazzleConf release track before API 2.0. At this point, DazzleConf 1.x is largely stable and has seen plenty of usage. However, it suffers architectually from a number of flaws, which is why version 2.0 is in development. This release, 1.3.0-RC1, stabilizes the changes in 1.3.0-M1 and 1.3.0-M2 and adds some changes of its own.
The features deprecated by this release -- dotted key paths, value validators, and @ConfSerialisers -- will be removed without replacement in version 2.0.
Bug fixes:
dazzleconf-ext-gson(#44)Deprecations:
@ConfKey. This is a strange way of specifying sub-paths, that I hope no one uses - #24ValueValidatorand@ConfValidator@ConfSerialisersMigration
Dotted key paths in
@ConfKeyare now disabled by default. Using them will throw an exception. To re-enable them, you have to set a flag inConfigurationOptions. This can be done like so:Migration checklist from 1.2.x:
ValueSerialiserimplementation, your code's behavior may be affected.MissingValueExceptionis now correctly thrown in the case where it should be thrown (MissingKeyExceptionused to be thrown instead).v1.3.0-M2: : Fixed Support for SnakeYaml VersionsCompare Source
This release fixes and officializes DazzleConf's support for SnakeYaml versions 1.15 through 1.33, and 2.0+. You may now use
dazzleconf-ext-snakeyamlwith any of these SnakeYaml versions.There are no changes to the core library or the other configuration formats.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.