chore: GitHub Releases page is stale and undersells active development

[Austin-s-h]

Summary

The current default GitHub Releases view makes Quilt look much less active than it actually is.

Right now, the repo has continued shipping new tagged versions, but the Releases page still appears outdated. Many users check Releases before Tags, so this creates the impression that development has slowed or stopped when that is not the case.

Problem

• The default Releases view on GitHub undersells active development.
• Existing tags are not consistently represented as published GitHub Releases.
• As a result, the public release history looks stale even though newer versions exist.

Request

Please backfill GitHub Releases for existing version tags and make GitHub Release publication part of the standard release flow going forward.

For each tag:

• Use the GitHub release flow with the existing tag.
• Generate release notes from the previous semver tag.
• Use intelligent version comparisons so GitHub auto-generates the correct diff and PR summary.

Example comparison:

6.3.1...7.3.0

Tags page:

https://github.com/quiltdata/quilt/tags

Why this matters

• The Releases tab is the default public signal of project activity for many users.
• An outdated Releases page makes the project look inactive or behind.
• Backfilling releases from existing tags is low effort and improves the project’s public presentation immediately.

Acceptance criteria

• Recent semver tags are published as GitHub Releases.
• Each release is attached to an existing tag rather than creating duplicate version markers.
• Generated release notes use the correct previous-version comparison.
• This becomes part of the normal release process so the Releases page stays current.