Revert "fix: publish beta releases to beta npm tag"

[aspiers]

This reverts commit a238d85 which didn't work. We'll just have to live with the bug that Changesets won't update the beta tag, only the latest tag.

Hopefully this bug won't persist once we have a stable release.

Summary by CodeRabbit

• Chores
  • Updated the beta release workflow to adjust how prerelease tagging is applied during the publishing process.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 22009fc

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

📝 Walkthrough

Walkthrough

The beta release workflow step in .github/workflows/release.yml was modified to remove the explicit --tag beta argument passed to the npm release command, changing from npm run release -- --tag beta to npm run release.

Changes

Cohort / File(s)	Summary
Workflow Release Configuration .github/workflows/release.yml	Removed explicit --tag beta argument from beta release command, relying on the release script's default behavior for beta tagging

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• chore: migrate release workflows to npm Trusted Publishers with unified workflow #52: Modifies the same beta publish step in the release workflow, standardizing how the npm release command is invoked
• fix: publish beta releases to beta npm tag #58: Directly inverts this change—modifies the same release workflow step with opposing flag handling (adds vs. removes --tag argument)

Poem

🐰 A flag was stripped, clean and bright,
The release flows now, without the blight,
Beta tags dance in scripts untold,
Simplicity's beauty, worth more than gold! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Revert "fix: publish beta releases to beta npm tag"' directly and clearly describes the main change in the pull request - reverting a specific commit that attempted to publish beta releases to the beta npm tag.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Lexicon Documentation Sync	✅ Passed	PR only modifies .github/workflows/release.yml, a configuration file excluded from the lexicon documentation sync check. No lexicon, README, or ERD files were modified.
Lexicons Styleguide Compliance	✅ Passed	This pull request does not modify any lexicon files in the /lexicons directory; it only changes .github/workflows/release.yml.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

.github/workflows/release.yml (1)

129-137: Misleading comment about automatic beta tagging.

The comment at lines 132-133 states that "changeset publish will automatically use the beta tag when in prerelease mode," but the PR description confirms this is not the case — Changesets only updates the latest tag. This comment should be updated to reflect actual behavior and document the known limitation.

📝 Suggested comment update

       # Beta-specific: Publish beta packages using changeset publish
       - name: Publish beta packages
         if: env.RELEASE_TYPE == 'beta'
-        # changeset publish will automatically use the beta tag when in
-        # prerelease mode and will create git tags for the release
+        # NOTE: Changesets does not automatically publish to the beta npm tag
+        # in prerelease mode - it publishes to 'latest'. This is a known limitation
+        # that will be addressed once a stable release exists.
+        # See: https://github.com/hypercerts-org/hypercerts-lexicon/pull/104
         run: npm run release

[aspiers]

This fixed it. For the record, now releases yield:

🦋  warn ===============================IMPORTANT!===============================
🦋  warn You are in prerelease mode so packages will be published to the beta
🦋  warn         dist tag except for packages that have not had normal releases which will be published to latest
🦋  warn ----------------------------------------------------------------------
🦋  info npm info @hypercerts-org/lexicon
🦋  info @hypercerts-org/lexicon is being published because our local version (0.10.0-beta.5) has not been published on npm
🦋  info @hypercerts-org/lexicon is being published to latest rather than beta because there has not been a regular release of it yet
🦋  info Publishing "@hypercerts-org/lexicon" at "0.10.0-beta.5"
🦋  success packages published successfully:
🦋  @hypercerts-org/lexicon@0.10.0-beta.5
🦋  Creating git tag...
🦋  New tag:  v0.10.0-beta.5

It's just a really stupid limitation of Changesets - it should be updating both dist tags not just latest.