Summary
The release published on 2026-06-14 and titled "ravencoin core v4.7.0" is attached to the Git tag v4.6.2snapshot instead of a new v4.7.0 tag. This creates a conflict between the release name and the underlying Git reference.
What was observed
The previous release before this one was v4.6.1 (2022-08-19). There was never a published release actually tagged v4.6.2 or v4.6.2snapshot — the v4.6.2snapshot tag appears to have been a pre-release/development reference that was reused when publishing the v4.7.0 binaries.
The release body itself notes:
"Note that the commit hash and the source code are not correct for this release."
This confirms the tag mismatch was unintentional.
Why this matters
Downstream projects and node operators that track Ravencoin versions by Git tag (e.g. to automate upgrade workflows, version pinning, or dependency checks) will read the tag as v4.6.2snapshot rather than v4.7.0. This causes:
- Incorrect version reporting in downstream tooling
- Confusion about whether
4.7.0 is actually released or still a snapshot
- Difficulty reliably distinguishing this release from any future
v4.7.0 tag that might be created
What the correct state should be
The release should be re-tagged as v4.7.0 to match the release title and the version advertised in the release notes. The v4.6.2snapshot tag should not be associated with a production v4.7.0 release.
If source code cannot yet be published (as noted in the release body), the release can remain as a binary-only release under the correct v4.7.0 tag until source is ready.
Summary
The release published on 2026-06-14 and titled "ravencoin core v4.7.0" is attached to the Git tag
v4.6.2snapshotinstead of a newv4.7.0tag. This creates a conflict between the release name and the underlying Git reference.What was observed
ravencoin core v4.7.0v4.6.2snapshotmasterThe previous release before this one was
v4.6.1(2022-08-19). There was never a published release actually taggedv4.6.2orv4.6.2snapshot— thev4.6.2snapshottag appears to have been a pre-release/development reference that was reused when publishing thev4.7.0binaries.The release body itself notes:
This confirms the tag mismatch was unintentional.
Why this matters
Downstream projects and node operators that track Ravencoin versions by Git tag (e.g. to automate upgrade workflows, version pinning, or dependency checks) will read the tag as
v4.6.2snapshotrather thanv4.7.0. This causes:4.7.0is actually released or still a snapshotv4.7.0tag that might be createdWhat the correct state should be
The release should be re-tagged as
v4.7.0to match the release title and the version advertised in the release notes. Thev4.6.2snapshottag should not be associated with a productionv4.7.0release.If source code cannot yet be published (as noted in the release body), the release can remain as a binary-only release under the correct
v4.7.0tag until source is ready.