Repository navigation
Prepare Sharp Kitchen for HACS release (blocked on credential architecture) - #1
Draft
aevans0001 wants to merge 45 commits into
Draft
aevans0001 wants to merge 45 commits into
aevans0001 wants to merge 45 commits into
Conversation
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.
Purpose
Prepare the existing working Sharp Kitchen integration for a future HACS release without changing its working authentication behavior.
Current safe-preparation status
0.9.0(not tagged or released)custom_components/sharp_kitchen/brand/icon.pngstrings.json: removedLatest validation
HARD BLOCKER — DO NOT MERGE OR RELEASE
The working implementation currently contains Sharp application authentication
material, including shared mTLS private-key material recovered from the official
application.
The formal public release must not embed that extracted private key. The
working values remain unchanged while a public-safe credential architecture is
researched.
Current research found that newer appliance revisions use Sharp's newer
SHARP HOME app and third-party account linking, but no public developer API,
user-created OAuth client, or per-installation mTLS provisioning mechanism has
been identified that resolves the existing Sharp Kitchen credential blocker.
This PR must remain draft and unmerged until that blocker is resolved and
the replacement design is explicitly approved.
Do not:
0.9.0The
mainintegration code remains unchanged; only the approved MIT LICENSEwas added directly to the default branch so HACS can recognize the repository
license.