Skip to content

fix: sync package.json version with VERSION file#741

Open
Gonzih wants to merge 1 commit intogarrytan:mainfrom
Gonzih:fix/package-json-version-sync
Open

fix: sync package.json version with VERSION file#741
Gonzih wants to merge 1 commit intogarrytan:mainfrom
Gonzih:fix/package-json-version-sync

Conversation

@Gonzih
Copy link
Copy Markdown

@Gonzih Gonzih commented Apr 1, 2026

Problem

package.json shows version 0.15.0.0 but VERSION file contains 0.15.1.0. These are out of sync.

This means npm show gstack version (if published), package.json version checks, and any tooling that reads package.json see the wrong version. Closes #399.

Fix

Updated package.json "version" field to match the canonical VERSION file: 0.15.1.0.

Notes

The VERSION file is the source of truth (used by gstack-update-check, CHANGELOG headers, etc). package.json should always mirror it. The /ship skill's idempotency check already guards against double-bumping VERSION — but it should also update package.json to keep these in sync after each bump.


sent from mStack

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.

bug: package.json version out of sync with VERSION file on main

1 participant