Skip to content

chore: update ktsu.Sdk to 2.21.1 [patch] - #245

Closed
matt-edmondson wants to merge 1 commit into
mainfrom
chore/sdk-2.21.1-lf-migration
Closed

chore: update ktsu.Sdk to 2.21.1 [patch]#245
matt-edmondson wants to merge 1 commit into
mainfrom
chore/sdk-2.21.1-lf-migration

Conversation

@matt-edmondson

Copy link
Copy Markdown
Contributor

Bumps ktsu.Sdk and its variants to 2.21.1 in global.json. File headers are migrated to the single line from COPYRIGHT.md, which is what the SDK writes into .editorconfig as file_header_template and IDE0073 enforces. Updates Color.Palette.* to Palette.*, and migrates SearchBox to the SearchBoxOptions API for ktsu.ImGui.Widgets 3.3.9.

Generated with Claude Code

Bumps ktsu.Sdk and its variants to 2.21.1 in global.json.

File headers are migrated to the single line from COPYRIGHT.md, which is what
the SDK writes into .editorconfig as file_header_template and IDE0073 enforces.

Updates Color.Palette.* to Palette.*, and migrates SearchBox to the SearchBoxOptions API for ktsu.ImGui.Widgets 3.3.9.
@matt-edmondson

Copy link
Copy Markdown
Contributor Author

Closing as obsolete — superseded by main.

This PR was part of the org-wide chore/sdk-2.21.1-lf-migration sweep from 2026-08-11. Every change it carries has since landed on main through other routes:

  • ktsu.Sdk 2.21.1 bumpmain is now on a later SDK (2.25.0+), so the global.json change is a downgrade.
  • License-header migration — the one-line // Copyright (c) 2023-2026 ktsu-dev contributors header is already on main.
  • .gitattributes LF normalization — already on main, byte-identical to this branch.
  • .editorconfig / .runsettings — already updated on main.
  • Any API adaptations — already present on main.

The PR is also in a conflicting state and would need a full rebase to produce a diff that is, by then, empty. Nothing here is worth recovering.

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.

1 participant