Why it matters
Releases & tags gives ForkMesh a concrete mechanism for tag and release operations tied to repository history. Browse tags, mark the current release, and cut new releases in seconds, release notes live in the repository like everything else.
Delivery metadata is part of a project, not a separate dashboard that should disappear during a migration. In ForkMesh, releases & tags addresses that need at the feature level, keeping the behavior close to the repository instead of buried in a detached hosted layer.
How ForkMesh handles it
ForkMesh handles releases & tags through the same split it uses across the product: ForkMesh keeps runs, logs, artifacts, releases, quality signals, installers, and downloads close to the mirrored repository.
The behavior is intentionally narrow: Browse tags, mark the current release, and cut new releases in seconds, release notes live in the repository like everything else. Outputs can be linked to commits and served by nodes instead of becoming opaque hosted-only assets.
Where it fits
Use releases & tags when shipping, validation, and release assets need to remain attached to the preserved repository.
It pairs with the rest of CI, releases & distribution because Releases & tags keeps tag and release operations tied to repository history connected to the repository, its signatures, and the nodes that serve it.