Missing GitHub Release/Tag for v1.0.0 (and v0.8.4) — release history out of sync with deployed version

[Mounika-Badadh]

Summary

The deployed validation service now shows version 1.0.0 in the UI, but there is no corresponding GitHub Release, Tag, or changelog entry to reflect this.

Current State

• Latest GitHub Release: v0.8.3 (Dec 12, 2025)
• Latest GitHub Tag: v0.8.3 (Dec 9, 2025)
• Deployed version (visible in UI): 1.0.0

It also appears that v0.8.4 was prepared (based on commits in Dec 2025 / Feb 2026) but was similarly never published as a formal GitHub Release or Tag.

Why This Matters

• Contributors and downstream users rely on GitHub Releases and Tags to understand what has changed between versions.
• The gap between v0.8.3 (last release) and 1.0.0 (deployed) represents a significant jump — especially crossing a major version boundary — with no documented changes.
• Automated tooling (dependency trackers, CI pipelines, etc.) that watches GitHub Releases will not be aware of the latest version.

Request

It would be very helpful if the team could:

1. Publish a GitHub Release and Tag for v1.0.0 with release notes summarizing what changed since v0.8.3.
2. Optionally backfill a release for v0.8.4 if it was deployed at some point.
3. Consider adding a CHANGELOG.md to the repository to make version history easier to follow going forward.

Thank you for the work on this project — the 1.0.0 milestone is a great achievement and it would be good to have it properly documented!

[aothms]

Thanks, we'll get to this. The team is currently at the bSI summit in Porto.