Repository navigation
www: remove Starlight attribution, update stale changelog page - #145
Merged
Merged
Conversation
- Drop the "Site built with Starlight" footer line and its now-unused i18n keys — Starlight is MIT-licensed with no attribution requirement, and it was just cluttering the footer. - docs/changelog.md hadn't been updated since v1.2.0 (2026-06-28); the package is now at v1.4.1. Added curated entries for v1.4.0, the v1.3.1-v1.3.3 patch run, and v1.3.0 (mock factory layer). Left out v1.4.1 deliberately — it's a docs-site-only translation fix with zero library code changes. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
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.
Summary
docs/changelog.md, which hadn't been touched since v1.2.0 (2026-06-28) while the package is now at v1.4.1. Added curated entries for:verifyContracts(),spinUpAll(),git-scenarios init,scenarioTest(), 2 new scenarios, 6 bug fixes@gfargo/git-scenarios/mocks)Aside (not addressed here)
Noticed while investigating:
release-please-config.jsontreats the whole repo as a single package with no path scoping, so conventional commits underwww/(docs site only) trigger real npm version bumps — that's how a docs-only fix produced v1.4.1 with no actual package diff from v1.4.0. Not fixing that here since it's a bigger call about the release process, but flagging it as the likely root cause of the changelog drifting out of sync going forward.Test plan
npm run buildcompletes cleanlyenandzh-cnrendered output🤖 Generated with Claude Code