Skip to content

changelog: Add entry for the boolean flag help change from the pflag 1.1.0 bump - #7683

Closed
janniklasrose wants to merge 2 commits into
mainfrom
janniklasrose/pflag-bool-flag-changelog
Closed

janniklasrose wants to merge 2 commits into
mainfrom
janniklasrose/pflag-bool-flag-changelog

Conversation

@janniklasrose

Copy link
Copy Markdown
Member

Changes

Add a .nextchanges/cli/ fragment for the user-visible effect of the pflag 1.1.0 bump in #7635: boolean flags now show [=true|false] in help output, and when a boolean flag is passed more than once, the last occurrence wins.

Why

#7635 was a dependabot PR and merged without a changelog entry; the review asked for one. Parsing of --flag=false is not new in pflag 1.1.0, only the help rendering is (spf13/pflag#453), so the entry describes the help change and the existing last-occurrence-wins behavior rather than claiming new parsing.

Tests

  • task check-changelog passes locally.
  • With a build of main: databricks version --debug --debug=false prints no debug logs, databricks version --debug=false --debug does, and databricks --help shows --debug[=true|false].

This pull request and its description were written by Isaac.

janniklasrose and others added 2 commits November 16, 2026 11:00
…1.1.0 bump

#7635 bumped pflag to 1.1.0 without a changelog entry. Its user-visible
effect is that help output now shows `[=true|false]` after boolean flags.
The entry also notes that the last occurrence of a repeated boolean flag
wins, which the new help syntax makes discoverable.

Co-authored-by: Isaac <no-reply@databricks.com>
@janniklasrose
janniklasrose marked this pull request as ready for review November 16, 2026 11:12
@janniklasrose
janniklasrose requested a review from a team as a code owner November 16, 2026 11:12
@pietern

pietern commented Nov 16, 2026

Copy link
Copy Markdown
Contributor

This was already the case. The bump only added it to the help output. I don't think this warrants a changelog entry.

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.

2 participants