Skip to content

Conversation

@bearomorphism
Copy link
Contributor

Changes

  1. Remove unreachable logic, such as setting dry_run = True while we already have get_next = True. The latter condition raises a GetNextExit() exception in the original code, so no effect if we set dry_run to True. Moreover, the original code is self.dry_run = True which is ineffective since we never use the member variable.
  2. Simplify things.
  3. Rename the variable get_next to next_version_to_stdout. The variable name get_next is very unclear and hard to guess what it will do. I think we can consider renaming the option in the next major release.
  4. (relate Not possible to use --get-next when changelog is enabled #1640) Replace NotAllowed related to --get-next option with warnings.
  5. Remove GetNextExit exception because we already have DryRunExit. --get-next is just --dry-run but doing less things IMO.

@bearomorphism
Copy link
Contributor Author

image

Is the branck v4-10-1 broken?

Copy link
Member

@woile woile left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Lee-W
Copy link
Member

Lee-W commented Nov 11, 2025

I just update the v4-10-1 branch. Could you please rebase from it again? We might need to come up with another release strategy, but this is what we have for the time being

@Lee-W Lee-W marked this pull request as draft November 11, 2025 01:50
@Lee-W Lee-W added this to the 4.10.1 milestone Nov 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants