Fix cursor bot

[clayauld]

Note

Use async_update_entry to set migration versions, add Bandit and types to CI, and tighten Flake8 config; update tests accordingly.

• Home Assistant integration:
  • Update async_migrate_entry in custom_components/satcom_forecast/__init__.py to pass version directly via hass.config_entries.async_update_entry(..., version=3/4).
• CI/Linting:
  • In .github/workflows/test.yml, install additional tools: bandit, types-aiofiles.
  • In .pre-commit-config.yaml, tighten Flake8 by removing E501 from --extend-ignore.
• Tests:
  • Adjust mocks in tests/test_init.py to reflect version updates via async_update_entry side effects.
  • Reformat long strings and f-strings across tests (no functional changes).

^{Written by Cursor Bugbot for commit 32850fe. This will update automatically on new commits. Configure here.}

[gemini-code-assist]

Summary of Changes

Hello @clayauld, 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 an issue where configuration entry versions might not have been correctly updated during migrations for the satcom_forecast custom component. The changes ensure that the version attribute is explicitly set when updating configuration entries, improving the reliability of the migration process. Additionally, the test suite has been refined to better simulate this behavior, providing more accurate validation of the migration logic.

Highlights

• Configuration Migration Logic: The configuration entry migration process for the satcom_forecast component has been updated to explicitly pass the version parameter to hass.config_entries.async_update_entry. This ensures that the config_entry object's version is correctly updated and persisted during migrations to versions 3 and 4.
• Improved Test Mocking: The MagicMock for hass.config_entries.async_update_entry in the test suite has been enhanced. It now uses a side_effect function that accurately simulates the behavior of updating both the data and version attributes of the mocked config_entry, leading to more robust and realistic test coverage for migration scenarios.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/test.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. ↩

[github-actions]

📊 Pull Request Analysis Report

🧪 Test Results

Metric	Value
Total Tests	244
✅ Passed	244
❌ Failed	0
⏭️ Skipped	0
💥 Errors	0
📈 Success Rate	100.0%

📋 Coverage Report

Metric	Value
Overall Coverage	81.6%
Total Lines	2789
Covered Lines	2276
Missing Lines	513

📁 File Coverage Breakdown

• __init__.py: 86.0%
• api_cache.py: 83.5%
• api_client.py: 84.5%
• api_config.py: 75.2%
• api_data_processor.py: 78.9%
• api_error_handler.py: 88.9%
• api_formatter.py: 94.2%
• api_models.py: 94.7%
• config_flow.py: 68.5%
• const.py: 100.0%

🎯 Recommendations

---

📊 Analysis generated by GitHub Actions • View detailed test report

[gemini-code-assist]

Code Review

This pull request updates the configuration migration logic to correctly use the version parameter in async_update_entry, which is the proper way to version config entries in Home Assistant. The tests have also been updated to reflect this change. My review includes suggestions to remove redundant code that is now handled by the updated async_update_entry call.

[github-actions]

🤖 Automated Code Review

🧪 Test Results

✅ All tests passed! Your changes don't break any existing functionality.

🔍 Linting Results Summary

✅ Black (Code Formatting) - PASSED

✅ Flake8 (Code Quality) - PASSED

✅ isort (Import Sorting) - PASSED

✅ MyPy (Type Checking) - PASSED

✅ Bandit (Security) - PASSED

✅ All Linting Checks Passed!

Great job! Your code meets all the linting standards.

---

This comment was automatically generated by GitHub Actions. Check the Actions tab for detailed logs.