Skip to content
This repository was archived by the owner on Jul 10, 2026. It is now read-only.

fix: reset version to 0.1.0 and remove erroneous 1.0.0 release - #2

Merged
grimnote merged 1 commit into
mainfrom
fix/reset-version-0.1.0
Apr 5, 2026
Merged

fix: reset version to 0.1.0 and remove erroneous 1.0.0 release#2
grimnote merged 1 commit into
mainfrom
fix/reset-version-0.1.0

Conversation

@grimnote

Copy link
Copy Markdown
Collaborator

Summary

  • Reverts package.json version from 1.0.0 back to 0.1.0
  • Removes auto-generated 1.0.0 CHANGELOG section, restores original 0.1.0 entry
  • The v1.0.0 GitHub release and tag have already been deleted from remote

Why

Semantic-release created v1.0.0 because no baseline tag existed — it defaulted to 1.0.0 on seeing feat: commits. A v0.1.0 tag will be pushed after merge to establish the correct baseline.

Test plan

  • package.json version is 0.1.0
  • CHANGELOG.md only has 0.1.0 section
  • After merge, v0.1.0 tag pushed as baseline
  • Next release from semantic-release starts from 0.1.x

🤖 Generated with Claude Code

Semantic-release created v1.0.0 because no baseline tag existed.
Reverts package.json to 0.1.0 and removes auto-generated 1.0.0
CHANGELOG section. The v1.0.0 GitHub release and tag have been
deleted from remote.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@grimnote
grimnote merged commit ca5a64c into mainApr 5, 2026
3 checks passed
@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@grimnote