Visitar URL original
YAML timestamps not handled properly with SnakeYaml 1.31 · Issue #32229 · spring-projects/spring-boot · GitHub
Skip to content

YAML timestamps not handled properly with SnakeYaml 1.31 #32229

Closed

Description

@bclozel

Forward port of issue #32228 to 2.7.x.

Activity

  1. added
    status: forward-portAn issue tracking the forward-port of a change made in an earlier branch
    on Sep 5, 2022
  2. added this to the 2.7.4 milestone on Sep 5, 2022
  3. added a commit that references this issue on Sep 5, 2022
    cca5ee8
  4. added and removed on Sep 5, 2022
  5. changed the title [-]Support for SnakeYaml 1.31[/-] [+]YAML timestamps not handled properly with SnakeYaml 1.31[/+] on Sep 5, 2022
  6. albertwangnz commented on Sep 15, 2022

    @albertwangnz

    Hi @bclozel , snakeyaml released 1.32. Will Spring Boot 2.7.4 support it? Thanks.

    Albert

  7. bclozel commented on Sep 17, 2022

    @bclozel
    MemberAuthor

    Yes it will support it, but the default managed version will not change.

  8. fabian-froehlich commented on Sep 27, 2022

    @fabian-froehlich

    Hi @bclozel is snakeyaml release 1.33 also supported by spring-boot 2.7.4? The changelog looks inconspicuous and our software passes alle tests. But I am not quite sure what snakeyaml really does in spring boot.

  9. sreekanth-tf commented on Sep 27, 2022

    @sreekanth-tf

    Hey there, May I know what kind of open source policy is preventing the spring boot from including the latest snakeyaml in its distribution? it looks like even 1.32, and 1.33 is also reported with security vulnerabilities, why can't spring-team consider a custom solution for its yaml processing?

  10. bclozel commented on Sep 27, 2022

    @bclozel
    MemberAuthor

    @fabian-froehlich it's only being used for parsing your application.yml, so if your configuration is parsed and your tests pass you should be good. I've just ran our entire test suite on the main branch against this new version and everything is green.

    @sreekanth-tf our upgrade policy describes the rationale here - we don't upgrade minor versions of third party dependencies in maintenance releases as this might cause behavior changes for applications. Right now, we don't feel like creating our own YAML parser is in scope for this project. Arguably, creating our own would not prevent CVEs anyway.

  11. bclozel commented on Sep 27, 2022

    @bclozel
    MemberAuthor

    @sreekanth-tf this would make Jackson a required dependency for all Spring Boot applications, which is not the case right now.

  12. sreekanth-tf commented on Sep 27, 2022

    @sreekanth-tf

    I got your point, thanks..... also jackson-dataformat-yaml internally depends on snakeyaml 🤣

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    status: forward-portAn issue tracking the forward-port of a change made in an earlier branchtype: bugA general bug

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions