New brands-proxy-api for providing integration icons

[magicl]

Describe the issue

I followed these instructions to add an icon for my new integration to home assistant as required to pass the hacs github actions

My PR was denied because we should now use the new brands-proxy-api to upload icons.

Suggested actions:

• Update the instructions referenced above to point to the new method
• Update the required github actions to check for brand images per the new brands-proxy-api

(Sorry if I added this issue in the wrong place. Could not find a better place to put it)

Screenshots

No response

[hacs-bot]

Thank you for opening an issue in the HACS.

Before proceeding, please verify the following:

Select the correct issue template:
HACS provides different templates for different types of bugs. Choosing the right template ensures you're asked the right questions and helps route your bug appropriately.

Complete the ENTIRE issue template:
Make sure you've read the issue guidelines and filled out every single field in the issue template, even if some fields seem unrelated to your specific situation.

Fill out everything, even if it seems unnecessary:
Don't skip fields because they "don't seem relevant" to your bug. The template asks for specific information because:

• Problems often have unexpected causes that surface through "unrelated" details
• What seems unrelated to you might be the key to solving your bug
• Incomplete information requires follow-up questions, delaying resolution
• The template is designed based on years of troubleshooting experience
• Missing information forces those helping to make assumptions, which can lead to wrong solutions

Issues with incomplete templates take significantly longer to resolve or may be closed without resolution.

If you're experiencing a similar bug:
If your bug is identical to an existing one, please:

• Add a 👍 reaction to the original issue description
• Subscribe to notifications on that issue to stay updated
• Do not add comments like "same here", "I have this too", or "+1"

Adding duplicate comments creates noise and makes it harder to track and resolve issues. Reactions help prioritize issues based on how many users are affected.

Getting help:
If you need assistance filling out the template or understanding your issue:

• Issue Guidelines - Detailed instructions for reporting issues
• HACS Discord - Community support and real-time help

What happens next:
Maintainers and community members will review your issue and may:

• Ask for additional information if the template is incomplete
• Provide a solution or workaround
• Label the issue appropriately for tracking
• Link it to related issues or pull requests

[brianegge]

I submitted two brands PRS. There were comments because I didn’t use the right form, which I fixed and then waited. So today they declined my PRs as well. I’m glad we can integrate our icons into our custom components which makes a lot more sense. HACS needs updated documentation and validator.

[dcapslock]

Also:

• HACS validation GitHub action will need to be updated.
• HACS Frontend to be rebuilt to pick up changes in brandsUrl() which now gets brand icons locally.

[loryanstrant]

I've also had my PR for a logo be denied due to the change.
This is a good change as it reduces the dependency and delay in releasing new custom components, but I'm keen to get the new validation action so it can pass and I can submit my integration to the HACS default repo.

[philrenda]

Same situation here. I submitted my integration but the brands check will fail since home-assistant/brands is no longer accepting custom integration PRs. (precipitation-radial-card) to hacs/default#5834

My repo already ships local brand icons at custom_components/precipitation_radial/brand/icon.png and icon@2x.png per the new brands proxy API. PR #5124 here looks like the right fix, just wanted to add another data point that this is blocking new submissions to hacs/default.

[MattXcz]

+1 on this one....