Skip to content

chore: bump version to 1.1.4#95

Merged
KailasMahavarkar merged 1 commit intomainfrom
chore/bump-version-to-1.1.4
Apr 22, 2026
Merged

chore: bump version to 1.1.4#95
KailasMahavarkar merged 1 commit intomainfrom
chore/bump-version-to-1.1.4

Conversation

@KailasMahavarkar
Copy link
Copy Markdown
Collaborator

Bumps package.json version from 1.0.5 (carried by the revert commit) to 1.1.4.

Why 1.1.4: the public history already advanced through v1.1.0..v1.1.3 on remote tags. This commit is a new post-v1.1.3 state (the revert is expressed as a forward commit because branch protection forbids non-fast-forward push). 1.1.4 is the next legitimate increment; it lets release-and-publish CI auto-create a matching v1.1.4 tag + GitHub release on merge.

Also cleaned up in this pass (local only, nothing to PR):

  • Deleted stale local tag v2.0.0 that pointed at the now-orphaned b12b0e0 commit. Remote never had v2.0.0 so no remote change needed.

Out of scope / needs manual attention:

  • ghcr.io container images: token lacks read:packages scope, cannot enumerate. If a v2.0.0 container was published, delete it via GitHub Packages UI.

Restored tree from 62f487e carried package.json version 1.0.5, but the public history already advanced through v1.1.0..v1.1.3. Bumping to 1.1.4 signals that this commit is a new post-v1.1.3 state (revert expressed as forward commit) and lets the release-and-publish CI auto-create a matching v1.1.4 tag + GitHub release on merge.

No code changes. Only package.json version field.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@KailasMahavarkar KailasMahavarkar merged commit 4b70df4 into main Apr 22, 2026
4 checks passed
@KailasMahavarkar KailasMahavarkar deleted the chore/bump-version-to-1.1.4 branch April 22, 2026 06:07
KailasMahavarkar added a commit that referenced this pull request Apr 22, 2026
Single-commit destructive revert. Tree equals 7131ac3 exactly EXCEPT for a one-line fix in skills/hyperstack/SKILL.md to unbreak CI.

Why the fix is needed: the 7131ac3 snapshot itself had an internal drift - src/internal/context-compiler.ts extracts the section heading "Role Registry" while skills/hyperstack/SKILL.md has "## Role Registry Details". `bun run compile:context` fails as a result and the verify job cannot pass. Admin-merge with failing required status checks is blocked by branch protection.

Minimal fix: rename the skill heading from "## Role Registry Details" to "## Role Registry" to match what the compiler already reads. This is the smallest possible change to make the 7131ac3 tree runnable in CI.

Everything else about the tree equals 7131ac3 (feat: rename using-hyperstack to hyperstack and implement 3-layer architecture) from 2026-04-15.

Wipes PRs #78..#95. 28 files changed vs prior main, +320 -101.

Follow-up still needed: target carries package.json version 1.1.3 which already has a tag. A version bump to 1.1.5 must land next so release-and-publish doesn't try to re-tag v1.1.3.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
KailasMahavarkar added a commit that referenced this pull request Apr 22, 2026
Single-commit destructive revert. Tree equals 7131ac3 exactly EXCEPT for a one-line fix in skills/hyperstack/SKILL.md to unbreak CI.

Why the fix is needed: the 7131ac3 snapshot itself had an internal drift - src/internal/context-compiler.ts extracts the section heading "Role Registry" while skills/hyperstack/SKILL.md has "## Role Registry Details". `bun run compile:context` fails as a result and the verify job cannot pass. Admin-merge with failing required status checks is blocked by branch protection.

Minimal fix: rename the skill heading from "## Role Registry Details" to "## Role Registry" to match what the compiler already reads. This is the smallest possible change to make the 7131ac3 tree runnable in CI.

Everything else about the tree equals 7131ac3 (feat: rename using-hyperstack to hyperstack and implement 3-layer architecture) from 2026-04-15.

Wipes PRs #78..#95. 28 files changed vs prior main, +320 -101.

Follow-up still needed: target carries package.json version 1.1.3 which already has a tag. A version bump to 1.1.5 must land next so release-and-publish doesn't try to re-tag v1.1.3.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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