chore: back-merge main into develop - #45
Merged
Merged
Conversation
release: Claude Code Native 5.0.0 — plaintext credentials closed, native login, install screen, session data, compliance
Back-merge of the v5.0.0 release merge commit, so develop is up to date with main and the 5.0.1 release pull request can be merged. Content no-op: main carries no change develop does not already have.
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.
Back-merge of the v5.0.0 release merge commit (
6fbc973), sodevelopis up to date withmainand the 5.0.1 release pull request (#44) can be merged — the ruleset onmainrequires the head branch to be up to date.Content no-op.
git diff origin/develop..HEADis empty: the only commitmaincarried thatdeveloplacked is the merge commit of #41, whose content was already ondevelop. This restores the genealogy, nothing else.Done as a pull request rather than
update-branchbecause thedevelopruleset requires every change to arrive through one (the API refused with Changes must be made through a pull request).🤖 Generated with Claude Code