Skip to content
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

chore(deps): update dependency org.virtuslab:scala-yaml to v0.3.0 #94

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 31, 2024

This PR contains the following updates:

Package Update Change
org.virtuslab:scala-yaml minor 0.0.8 -> 0.3.0

Warning

Some dependencies could not be looked up. Check the warning logs for more information.


Release Notes

VirtusLab/scala-yaml (org.virtuslab:scala-yaml)

v0.3.0

Compare Source

What's Changed

Full Changelog: VirtusLab/scala-yaml@v0.2.0...v0.3.0

v0.2.0

Compare Source

What's Changed

  • Fixed a bug (#​314) where decoding as Any lost precision due to preference of Float over Double. Side effect of this change is that this is a breaking change as all decimal numbers in range of double precision will be parsed as Double instead of Float.
  • Fixed a bug (#​313) where an ellipsis was parsed as a document end marker even when it was a part of a value in a mapping.
  • Fixed a bug (#​281) where newlines were escaped in literal scalar blocks.
  • Fixed a bug (#​258) where backslashes were escaped in single-quoted strings.
  • Fixed a build configuration bug (#​228) which caused publishing of scaladocs for integration tests module.
  • Fixed a bug (#​222) where some valid numeric values were not parsed as numeric types.
  • Fixed a bug (#​216) where non-printable characters were not escaped into their readable form when printing yaml.
  • Provided an improved error message for #​120 which occurs when a !!null tag is encountered where a non-optional type is expected in target structure.
  • Fixed a bug (#​86) where mapping without a value was not parsed correctly.
  • Fixed parsing of folded scalar values reported as bug #​60, now folded scalars are parsed according to the spec.
  • Added a new feature allowing to use default parameter values in deserialization to case classes for which YamlCodec or YamlDecoder is derived (#​215).

New Contributors

Full Changelog: VirtusLab/scala-yaml@v0.1.0...v0.2.0

v0.1.0

Compare Source

What's Changed

New Contributors

Full Changelog: VirtusLab/scala-yaml@v0.0.8...v0.1.0


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/org.virtuslab-scala-yaml-0.x branch from 850b378 to f53ef48 Compare July 26, 2024 11:14
@renovate renovate bot changed the title chore(deps): update dependency org.virtuslab:scala-yaml to v0.1.0 chore(deps): update dependency org.virtuslab:scala-yaml to v0.2.0 Jul 26, 2024
@renovate renovate bot force-pushed the renovate/org.virtuslab-scala-yaml-0.x branch from f53ef48 to 603c79d Compare July 30, 2024 14:13
@renovate renovate bot changed the title chore(deps): update dependency org.virtuslab:scala-yaml to v0.2.0 chore(deps): update dependency org.virtuslab:scala-yaml to v0.3.0 Jul 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants