Skip to content

revert: destructive reset of repo state to v1.0.0#98

Closed
KailasMahavarkar wants to merge 1 commit intomainfrom
chore/reset-to-v1.0.0
Closed

revert: destructive reset of repo state to v1.0.0#98
KailasMahavarkar wants to merge 1 commit intomainfrom
chore/reset-to-v1.0.0

Conversation

@KailasMahavarkar
Copy link
Copy Markdown
Collaborator

Destructive reset. Tree equals v1.0.0 (commit 5649490, 2026-04-10) exactly. 226 files restored. Wipes all work since v1.0.0.

After merge I will delete:

  • all remote tags v1.0.1..v1.1.5
  • GitHub release v1.1.5
  • recreate hyperstack-mcp docker container on v1.0.0 image

Verified locally: bun install clean, bun test 8/8 pass, bun run build exit 0.

Sets main tree equal to v1.0.0 (2026-04-10, commit 5649490). Wipes all work after v1.0.0 including v1.0.1..v1.1.5 eras.

Tree equals v1.0.0 tree exactly. 226 files restored. package.json reverts to version 1.0.0. CI workflow at v1.0.0 only runs install + test + build (no compile:context, no skills:index), both verified clean locally (8 tests pass, tsc exits 0).

After this lands: all tags v1.0.1..v1.1.5 will be deleted from remote, GitHub release v1.1.5 will be deleted, docker container will be recreated on the v1.0.0 image.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@KailasMahavarkar
Copy link
Copy Markdown
Collaborator Author

Superseded: user wants version reset only, not code reset.

@KailasMahavarkar KailasMahavarkar deleted the chore/reset-to-v1.0.0 branch April 22, 2026 07:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant