Skip to content

chore: sync main into develop after v0.1.5#14

Merged
explosivebit merged 3 commits into
developfrom
chore/sync-main-into-develop-after-v0.1.5
May 4, 2026
Merged

chore: sync main into develop after v0.1.5#14
explosivebit merged 3 commits into
developfrom
chore/sync-main-into-develop-after-v0.1.5

Conversation

@explosivebit
Copy link
Copy Markdown
Contributor

Brings v0.1.5 release commits (version bump 0.1.4→0.1.5 in package.json + template/package.json) back into develop per Git Flow §2.5 step 4. Without this back-merge develop forever lags main on version, and the next release/v0.1.6 cut would create merge conflicts.

Patch release: ships the v0.1.4 docs marketing rewrite (already on main, never reached the npm tarball because v0.1.4 was tagged before the docs PR landed) plus this branch's release-prep additions: physical LICENSE file, CHANGELOG.md, README.ru.md declared in files, demo block aligned with real bin output, absolute badge URLs.

Refs: PRD-001
Patch release: ships v0.1.4 docs rewrite + this branch's release-prep
(LICENSE, CHANGELOG.md, README.ru in tarball, demo fix, absolute badge
URL). Refs PRD-001.
@explosivebit explosivebit merged commit 4a7697f into develop May 4, 2026
3 checks passed
@explosivebit explosivebit deleted the chore/sync-main-into-develop-after-v0.1.5 branch May 4, 2026 18:32
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