Skip to content

docs: sync README and landing page with v3.5.4 / 10 Premium languages#70

Merged
heznpc merged 1 commit intomainfrom
docs/sync-readme-v3.5.4
Apr 10, 2026
Merged

docs: sync README and landing page with v3.5.4 / 10 Premium languages#70
heznpc merged 1 commit intomainfrom
docs/sync-readme-v3.5.4

Conversation

@heznpc
Copy link
Copy Markdown
Owner

@heznpc heznpc commented Apr 10, 2026

Summary

The v3.5.4 release bumped manifest.json and package.json (#69) but the docs were not regenerated. README and the landing page still advertised v3.5.0 and 6 Premium languages, even though src/lib/constants.js already has 10 entries in PREMIUM_LANGUAGES (added zh-TW, pt-BR, ru, vi).

This PR brings the docs back in sync with the code.

Changes

  • Ran npm run docs to update VERSION / LANG_COUNT markers in README.md and docs/index.html
    • v3.5.0v3.5.4
    • 33 languages32 languages (10 Premium + 22 Standard, excluding English)
  • Manually updated the README Premium table (6 → 10 entries) and trimmed the Standard list accordingly. scripts/generate-docs.js doesn't touch these tables.
  • Updated the Tech Stack row 570+ × 6 languages× 10.
  • Applied the same Premium table / Standard list / 6 → 10 changes to the 6 i18n README variants under docs/i18n/.

Verification

  • npm run lint — clean
  • npm run docs — idempotent after these edits (no further changes)
  • npm test — 309 / 309 passing (run earlier in the session)
  • npm run build:firefox — succeeds

Test plan

  • CI green
  • Spot-check rendered README on GitHub for the new Premium table and removed Standard entries
  • Spot-check landing page (docs/index.html) shows v3.5.4 in hero badge

🤖 Generated with Claude Code

The v3.5.4 release bumped manifest.json and package.json but the docs were
not regenerated. README and the landing page still advertised v3.5.0 and
6 Premium languages even though src/lib/constants.js has 10 in
PREMIUM_LANGUAGES (added zh-TW, pt-BR, ru, vi).

Changes:
- Run scripts/generate-docs.js to update VERSION / LANG_COUNT markers in
  README.md and docs/index.html (v3.5.0 -> v3.5.4, 33 -> 32 languages).
- Manually update the README Premium table (6 -> 10 entries) and shrink
  the Standard list accordingly (the script does not touch these).
- Update the README Tech Stack row "570+ x 6 languages" -> "x 10".
- Apply the same Premium table / Standard list / "6 -> 10" changes to
  the 6 i18n README variants under docs/i18n/.

Verified:
- npm run lint clean
- npm run docs is idempotent after these edits
- npm test 309/309 passing (run earlier in the session)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@heznpc heznpc merged commit 7517b37 into main Apr 10, 2026
2 checks passed
@heznpc heznpc deleted the docs/sync-readme-v3.5.4 branch April 10, 2026 10:35
heznpc added a commit that referenced this pull request Apr 10, 2026
The Auto-update docs workflow has been failing on every push to main
since v3.4.0 (10+ consecutive runs as of v3.5.4) with:

  remote: Permission to heznpc/skillBridge.git denied to github-actions[bot].
  fatal: ... The requested URL returned error: 403

Root cause: docs.yml had no permissions block, so GITHUB_TOKEN defaulted
to read-only. The script ran fine, the local commit succeeded, only the
final git push was rejected. This was an inadvertent omission — the
sibling release.yml workflow already has the same permissions block.

Result: every release since v3.4.0 has had stale README and landing
page until someone notices and fixes it manually (most recently #70).

Changes:
- Add job-level "permissions: contents: write" matching release.yml.
  Job-level (not workflow-level) keeps the principle of least privilege.
- Add workflow_dispatch trigger so the fix can be validated immediately
  via "gh workflow run docs.yml" instead of waiting for the next real
  release to flush out any further issues.
- Bump node-version 20 -> 22 to match the recent ci.yml upgrade
  (5862443 chore: upgrade CI to Node 22).

Out of scope (separate PR):
- Deprecation warning about actions/checkout@v4 + actions/setup-node@v4
  using internal Node 20 (removed 2026-09-16). That's a repo-wide actions
  version sweep across multiple workflows.

Co-Authored-By: Claude Opus 4.6 (1M context) <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