Changesets in release workflow

[tk-o]

Actual outcomes

The Release workflow requires to be tweaked, as it was incorrectly executed for a merge commit into main:
https://github.com/namehash/ensnode/actions/runs/15632556411/job/44040019738

Expected outcomes

The Release workflow run executed correctly:
https://github.com/namehash/ensnode/actions/runs/15584470009/job/43887182506

Context

What's interesting, looking at the Changesets dependency, it got some updates released in May that change how the tool treats private packages:

• Fixed a crash in pre mode when trying to version private packages when tagging for private package is disabled changesets/changesets#1668
• Ignore packages without version during prerelease changesets/changesets#1589

Possibly, we need to:

• lock the version of dependencies for Changesets tool
• update our Release workflow on CI to work with the latest Changesets version

[shrugs]

after investigation, this is likely caused by:

1. changesets is creating get tags to track the publishing of private packages
2. The changeset CLI thinks that this is successful
3. The tags do not exist in our repo
4. subsequent executions caused by merging to main without a changeset patch (which short-circuits the cli and causes it to upsert the release pr) sees the missing tags, and assumed that the private packages need to be published again

the solution is to figure out why the git tags are not in our repo — permissions?

[shrugs]

this describes the offending behavior and proposes a fix

changesets/action#500