Skip to content

Release sqlparser 0.56.1 (backport/fix release) #1952

Closed as not planned
Closed as not planned

Description

@crepererum

Since DataFusion has fallen a bit behind, having a stable intermediate step which we could use before jumping to 0.57 and beyond would be nice. Sadly, we cannot use 0.56 due to #1898. So we would like to have 0.56.0 + #1899 = 0.56.1.

Activity

  1. alamb commented on Jul 17, 2025

    @alamb
    Contributor

    I will plan to make a release candidate later today or tomorrow.

    FYI @iffyio (No action required on your part, just FYI that I plan to make a patch release)

  2. self-assigned this
    on Jul 17, 2025
  3. changed the title [-]Release 0.56.1 (backport/fix release)[/-] [+]Release `sqlparser-rs` 0.56.1 (backport/fix release)[/+] on Jul 18, 2025
  4. changed the title [-]Release `sqlparser-rs` 0.56.1 (backport/fix release)[/-] [+]Release 0.56.1 (backport/fix release)[/+] on Jul 18, 2025
  5. changed the title [-]Release 0.56.1 (backport/fix release)[/-] [+]Release sqlparser ~0.56.1~ `0.57.0` (backport/fix release)[/+] on Jul 18, 2025
  6. changed the title [-]Release sqlparser ~0.56.1~ `0.57.0` (backport/fix release)[/-] [+]Release sqlparser 0.56.1 (backport/fix release)[/+] on Jul 18, 2025
  7. alamb commented on Jul 18, 2025

    @alamb
    Contributor

    It turns out backporting #1898 would break other users (it changes the AST and this is not SemVer compatible with current 0.56.0).

    Thus I can not complete this task as specified and am closing this issue as I don't think it is possible to complete as specified

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions