chore(release): prep for v0.1.5 — LICENSE + CHANGELOG + tarball manifest + demo fix#12
Merged
Merged
Conversation
… in files package.json#license said MIT for several releases but the physical LICENSE file was missing - both READMEs linked to it from the badge and the footer, so the npm landing page rendered a broken link next to the MIT badge. Add the standard MIT text (matching the parent ForgePlan/forgeplan repo) and declare it in the files array so the tarball ships it. Also declare README.ru.md and the upcoming CHANGELOG.md in the files array. README.ru.md was already shipping silently because npm auto-includes README variants; promote that to an explicit declaration so audit trails match the actual tarball contents. CHANGELOG.md will be added in a follow-up commit on this branch. Refs: PRD-001
…tion docs/USAGE.md links to CHANGELOG.md for v0.1.3 Windows-fix context but the file did not exist - this PR fills that gap. Format follows Keep a Changelog 1.1.0; SemVer link refs follow keepachangelog conventions. Sections: Unreleased (this prep branch + the upcoming v0.1.5), 0.1.4 (today's main release), 0.1.3 / 0.1.2 (auto-published earlier today), 0.1.1 / 0.1.0 (initial attempts). Refs: PRD-001
Docs auditor caught two regressions: the 60-second demo block printed → appended .forgeplan-web/ to .gitignore plus a single ✓ ready line, while bin/forgeplan-web.mjs:94 actually prints → created .gitignore (added .forgeplan-web/) on first run and tails ✓ ready with two extra hint lines (start invocations). Same gap in README.ru.md. Pick the first-run case (more honest for a tutorial), include all real lines, add a follow-up note that repeat runs flip created → appended and creating → updating. Cross-platform CI badge previously linked to relative .github/workflows/smoke.yml — that target only resolves on github.com. On the npm landing it 404s. Switch to absolute https://github.com/ForgePlan/forgeplan-web/actions/workflows/smoke.yml (matches the CI status badge pattern just above it). Also tighten docs/CONTRIBUTING.md:122 wording from mirrors guides/GIT-FLOW-GUIDE.ru.md §2.5 to expands ... with the GitHub Release UI step + provenance publishing flow — accurate; the file documents 6 steps where the guide §2.5 has 4. Refs: PRD-001
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Multi-expert audit before cutting v0.1.5 flagged 2 CRITICAL blockers and several HIGH/MEDIUM findings. This PR closes all of them on develop so release/v0.1.5 cuts cleanly. Refs PRD-001.