chore: add v3.2.0 release entry to Flatpak metainfo#80
Conversation
The Flatpak metainfo.xml release list lagged behind by one entry — only 3.1.2 was the most recent. Adds 3.2.0 release notes so users browsing appstream metadata see the Intel-Aware Edition changelog. The two yml manifests still reference 3.1.0 wheels with SHA256 hashes attached. Updating those requires building a 3.2.0 wheel and regenerating the hash, which is a release-publish task rather than a version-sync task — left for whoever publishes 3.2.0 to PyPI/Flathub. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
There was a problem hiding this comment.
Code Review
This pull request updates the Flatpak metainfo file to include release notes for version 3.2.0, detailing the new "Intel-Aware Edition" features such as threat-tint borders, character status docks, and EVE Local channel log tracking. A review comment points out that the version 3.2.0 is inconsistent with hardcoded version strings in the source code that still refer to version 2.2, which should be updated to ensure consistency.
| </branding> | ||
|
|
||
| <releases> | ||
| <release version="3.2.0" date="2026-04-26"> |
There was a problem hiding this comment.
The version 3.2.0 added here is inconsistent with several hardcoded version strings in the source code. For example, in src/argus_overview/ui/main_window_v21.py, the class docstring (line 74) and the initialization log message (line 167) still refer to v2.2. Since the stated goal of this pull request is to "sync remaining version refs," these internal references should be updated to match the release version to ensure consistency across the application and its metadata.
Summary
The Flatpak metainfo.xml release list lagged behind by one entry — only 3.1.2 was the most recent. Adds 3.2.0 release notes so users browsing appstream metadata see the Intel-Aware Edition changelog.
This is debt item #3 from the post-v3.2.0 audit ("sync remaining version refs").
Files NOT updated and why
The two yml manifests (`io.github.aretedriver.ArgusOverview.yml`, `io.github.aretedriver.ArgusOverview.flathub.yml`) still reference `argus_overview-3.1.0-py3-none-any.whl` with SHA256 hashes. Updating those requires:
That's a release-publish task, not a version-sync task. Left for whoever ships 3.2.0 to PyPI/Flathub. Note that 3.1.0 is the version on PyPI today — the yml files were already stale through 3.1.1 and 3.1.2.
Test plan
🤖 Generated with Claude Code