Skip to content

fix: remove hardcoded version field from composer.json - #1

Open
square360-george wants to merge 1 commit into
mainfrom
fix/remove-hardcoded-composer-version
Open

fix: remove hardcoded version field from composer.json#1
square360-george wants to merge 1 commit into
mainfrom
fix/remove-hardcoded-composer-version

Conversation

@square360-george

Copy link
Copy Markdown
Member

Removes the hardcoded "version": "1.0.1" from composer.json. Composer's VCS driver skips any tag whose name disagrees with an in-file version field, so the next tag on this repo would silently fail to publish to packages.square360.com — exactly what hit square360/pantheon-lando-defaults v0.2.0 today. The tag is the version; the field must go.

🤖 Generated with Claude Code

A stale version field makes Composer's VCS driver skip any tag whose
name doesn't match it, so new tags silently never publish to Satis
(bit square360/pantheon-lando-defaults on v0.2.0, 2026-06-04). VCS-tagged
packages must omit the field — the tag is the version.

Co-Authored-By: Claude Opus 4.8 <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