chore: bump version to 0.62.0#32
Merged
fmguerreiro merged 1 commit intomainfrom Apr 26, 2026
Merged
Conversation
2 tasks
fmguerreiro
added a commit
to fmguerreiro/pgmold
that referenced
this pull request
Apr 26, 2026
…#272) The 0.62.0 release (fmguerreiro/datafusion-sqlparser-rs#32) renames Statement::Comment.relation to table_name for consistency with sibling AST nodes (AlterPolicy.table_name, CreatePolicy.table_name, DropPolicy.table_name, AlterTrigger.table_name). pgmold-293's audit had concluded the bump was Cargo.toml-only because pgmold matched Statement::Comment { .. } without field-name destructure. That audit was stale: pgmold-273 (e860e3d) had since added a destructure that bound `relation`. This commit therefore also: - renames pgmold's internal CommentStatement.relation -> table_name to mirror the upstream AST. - aliases the field at the destructure site to `partner_table` so the Trigger arm's `let (table_schema, table_name) = extract_qualified_name(...)` doesn't shadow it. Discovered-from: pgmold-293.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Minor version bump 0.61.1 → 0.62.0. Per the README convention, any change to the typed AST is technically breaking and warrants a
0.(N+1)bump.Bundled fork-side work since 0.61.0:
Statement::Comment.relation→table_namefor consistency with sibling AST nodes (AlterPolicy.table_name,CreatePolicy.table_name,DropPolicy.table_name,AlterTrigger.table_name). PostgreSQL: rename Statement::Comment.relation to table_name #31COMMENT ON FUNCTION/PROCEDURE/AGGREGATEnow parse argmode and argname tokens in the argument list, matching PostgreSQL server syntax. PostgreSQL: COMMENT ON FUNCTION/PROCEDURE/AGGREGATE accepts argmode/argname/VARIADIC #28 (already shipped in 0.61.1; documented in 0.62.0 changelog since 0.61.1 had no per-version file).CommentObject,AlterType, andAlterDefaultPrivileges(no behavior change). PostgreSQL: cleanup CommentObject, AlterType, AlterDefaultPrivileges #30Files
Cargo.toml— version0.61.1→0.62.0changelog/0.62.0.md— new fork-only changelog entryCargo.lockis gitignored on this fork (per the upstream library convention) so no lockfile update is part of this PR.Test plan
cargo publishfrom the maintainer's workstation.