fix: revert partial 30.1.1 release to allow clean re-release

[craigcarlyle]

Summary

• Reverts the chore(release): 30.1.1 commit that was pushed by a partially-failed semantic-release run.
• The previous run successfully pushed the version bump and tag but failed to publish to npm (EOTP error) or create a GitHub release.
• The v30.1.1 tag has already been deleted.
• Once this merges, semantic-release will trigger and cleanly create 30.1.1 with OIDC npm publishing.

Test plan

• Merge and verify the Release workflow succeeds, publishing @doist/reactist@30.1.1 to npm.

Made with Cursor

[doist-release-bot]

🎉 This PR is included in version 30.1.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[doistbot]

This PR reverts a partial version bump to allow the release pipeline to cleanly retry publishing version 30.1.1. Resolving this will help unblock the pipeline and successfully publish the package. However, keeping the current fix: prefix might inadvertently include this revert in the newly generated release notes, so consider using a non-release commit type like chore: when merging to keep the changelog clean.

_{Share Feedback • Review Logs}

[doistbot]

[P2] Reverting the version files alone does not fully restore the original 30.1.1 release state if this branch lands with its current fix: conventional commit type. semantic-release generates notes from commits since v30.1.0, so the recreated 30.1.1 will also include this revert as an extra bug-fix entry.

Use a non-release commit type for the revert (for example chore:) or override the squash commit title so the regenerated 30.1.1 only contains the original #1025/#1026 fixes.

[rfgamaral]

✅