Revert HACS zip release automation

[eXPerience83]

User description

Motivation

• The previously added HACS ZIP release automation and the additional keys in hacs.json introduced a publish path that breaks releases, so the integration must be restored to the prior stable state.

Description

• Remove the GitHub Actions workflow file .github/workflows/release-asset.yml that created and uploaded a ZIP release asset.
• Remove the zip_release and filename fields from hacs.json to restore the previous HACS metadata format.
• Apply import-order fixes and formatting to ensure repository linting and style consistency.

Testing

• Ran ruff check --fix --select I . and the check passed.
• Ran ruff check . and the check passed.
• Ran black . and formatting completed with no changes required beyond the applied formatting.

---

Codex Task

---

PR Type

Bug fix

---

Description

• Removes GitHub Actions workflow for ZIP release automation

• Deletes zip_release and filename fields from hacs.json

• Reverts breaking changes to restore stable release state

---

Diagram Walkthrough

flowchart LR
  A["Release Automation<br/>Workflow"] -->|removed| B["Stable Release<br/>State"]
  C["HACS Metadata<br/>Fields"] -->|removed| B

Loading

File Walkthrough

Relevant files

Bug fix

release-asset.yml Remove release ZIP automation workflow                                      .github/workflows/release-asset.yml Removes entire GitHub Actions workflow file for ZIP asset creation Eliminates automated ZIP archive building on release publication Deletes release asset upload step using softprops/action-gh-release +0/-46    hacs.json Remove ZIP release configuration from HACS metadata            hacs.json Removes zip_release boolean field Removes filename field specifying archive name Restores previous HACS metadata format +0/-2

---

[gemini-code-assist]

Summary of Changes

Hello @eXPerience83, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses critical issues with the previously implemented HACS ZIP release automation by reverting the changes that introduced instability. It removes the problematic GitHub Actions workflow and specific configuration fields from hacs.json, thereby restoring the integration to a stable, functional state and ensuring reliable release processes.

Highlights

• Reverted HACS ZIP Release Automation: The GitHub Actions workflow file responsible for creating and uploading ZIP release assets has been removed to address issues with the previous automation.
• Updated HACS Configuration: The zip_release and filename fields were removed from hacs.json to restore the previous HACS metadata format, which was causing release breaks.
• Code Style Consistency: Import-order fixes and formatting were applied to ensure repository linting and style consistency, although specific diffs for these changes are not provided in the patch.

Changelog

• hacs.json
  • Removed the zip_release field.
  • Removed the filename field.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/release-asset.yml

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

No code suggestions found for the PR.

[gemini-code-assist]

Code Review

The pull request successfully reverts the HACS zip release automation by removing the zip_release and filename fields from hacs.json and deleting the corresponding GitHub Actions workflow. These changes correctly restore the integration to its previous stable release state. The resulting hacs.json manifest is valid and adheres to HACS metadata standards.