Skip to content

chore: sync main into develop after v0.1.6#21

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

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

Conversation

@explosivebit
Copy link
Copy Markdown
Contributor

Back-merge per Git Flow §2.5 step 4. Brings v0.1.6 commits (version bump, CHANGELOG reorg) back into develop so feature branches start from the latest baseline.

Patch release shipping the security tactical S1 batch (PRD-002): four CWE fixes that landed on develop in PR #18 but never reached the npm tarball at v0.1.5. Reorganises CHANGELOG so 0.1.6 has a Security section (the one this release is about), 0.1.5 has Added / Fixed (docs marketing rewrite + en/ru + LICENSE/CHANGELOG/hero — already shipped to npm at v0.1.5). [Unreleased] is empty.

Refs: PRD-002, EVID-009
Patch release. Ships PRD-002 S1 batch to npm: CWE-78 FORGEPLAN_BIN
regex, CWE-59 update symlink-guard, CWE-770 spawn concurrency cap,
CWE-1357 build --ignore-scripts. Plus the docs rewrite that was meant
for 0.1.5 but landed on develop after that tag. Refs PRD-002 EVID-009.
@explosivebit explosivebit merged commit e07304f into develop May 5, 2026
3 checks passed
@explosivebit explosivebit deleted the chore/sync-main-into-develop-after-v0.1.6 branch May 5, 2026 07:18
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