Skip to content

docs: align package README badges with kiritan's (closes #66) - #69

Merged
otnc merged 1 commit into
mainfrom
feat/package-readme-badges
Sep 22, 2026
Merged

otnc merged 1 commit into
mainfrom
feat/package-readme-badges

Conversation

@otnc

@otnc otnc commented Sep 22, 2026

Copy link
Copy Markdown
Owner

Summary

  • Fix bug(s)
  • New feature(s)
  • Others

Each sub-package README (@kiritan/runtime, @kiritan/middleware, @kiritan/deepl, @kiritan/google-translate, @kiritan/free-translate) had only an npm version badge. kiritan's own README has four: npm version, CI status, license and Node engine range. Added the same three to each of the other five, pointing at the repo-wide ci.yml and license (shared across packages) and each package's own npm name for the version/Node badges.

Docs only.

Why?

closes #66 — badge set was inconsistent between the main package and the rest.

Related issue(s)

closes #66

Check

  • Check if duplicate PR(s) already exist.
  • Read CONTRIBUTING.md (rules)
  • Run npm run check (lint & format)
  • Run npm run typecheck
  • Run npm run test (functions test)
  • Run npm run build (dist/)
  • (optional) Run npm run test:coverage and check nothing new went uncovered

@otnc
otnc merged commit 730cc9e into main Sep 22, 2026
4 checks passed
@otnc
otnc deleted the feat/package-readme-badges branch September 22, 2026 13:43
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