fix: Kiro native authentication and doctor repair; prepare CLI 0.4.183 - #31
Merged
Conversation
yunze7373
changed the title
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.
Fix Kiro's generated MCP configuration so successful OAuth consent is not overridden by a literal environment-variable Bearer header. Kiro now uses native HTTP OAuth by default and supports explicit --auth key across setup and MCP commands.
Add offline doctor --client kiro diagnostics and explicit --fix migration with backups, authentication conflict detection, preservation of other servers and client preferences, and fail-closed handling of unsupported configurations. Update guidance and tests. Remove the retired bundled Kiro package assets already included in this branch.
Prepare CLI/npm 0.4.183; hosted MCP version is unchanged. Validation: 219 tests and lint passed locally, package dry run and CLI release metadata check passed. CI covers Windows, Linux and macOS with Node 20/22.