Skip to content

hotfix, originally in PR4428 - #463

Merged
costdev merged 1 commit into
release_1.4.0from
merge-hotfix
Mar 16, 2026
Merged

costdev merged 1 commit into
release_1.4.0from
merge-hotfix

Conversation

@afragen

@afragen afragen commented Mar 16, 2026

Copy link
Copy Markdown
Contributor

accidentally reverted in release_1.3.0 to main

accidentally reverted in release_1.3.0 to main

Signed-off-by: Andy Fragen <andy@thefragens.com>
@github-actions

Copy link
Copy Markdown
Contributor

colincwc
colincwc previously approved these changes Mar 16, 2026
@afragen

afragen commented Mar 16, 2026 •

Copy link
Copy Markdown
Contributor Author

Doesn’t seem like I have permission to merge cause it’s my PR

@fairpm fairpm deleted a comment from colincwc Mar 16, 2026

@costdev costdev left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Documenting

The accident in the Updater::upgrader_source_selection() method occurred when:

  1. release_1.3.0 was merged into main with a parameter change to the method in this commit
  2. main was subsequently merged into release_1.4.0 in this commit.

This produced a merge conflict:

  • A parameter type change was made in the method in release_1.3.0
  • The static keyword was added to the method in release_1.4.0 (#428)

Rather than both changes being included, the merge conflict was resolved by rejecting the static keyword and only including the parameter type change coming in from main.

Easily missed, and we've found it now.

@costdev
costdev merged commit 1188a3d into release_1.4.0 Mar 16, 2026
3 checks passed
@costdev
costdev deleted the merge-hotfix branch March 16, 2026 23:29
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.

4 participants