Repository navigation
chore: merge upstream tag 'v18.0.0' - #158
ReenigneArcher wants to merge 9 commits into
Conversation
Co-authored-by: Anthony Fu (via agent) <reg-github-bot@antfu.me>
Co-authored-by: Codex <codex@openai.com> Co-authored-by: Anthony Fu (via agent) <reg-github-bot@antfu.me>
Bundle ReportChanges will decrease total bundle size by 18.23kB (-7.84%) ⬇️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: contribkit-esmAssets Changed:
Files in
Files in
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #158 +/- ##
=============================
=============================
Continue to review full report in Codecov by Harness.
|
|



Description
Integrates SponsorKit v18.0.0 after the previous v17.1.1 sync. The upstream commit is
14d0ea2d8043d893483d12dff13eeacaf0059456; the downstream base is3a4e0fff1dbb94e9dc7dfba229d5d2b4775687b8.CONTRIBKIT_*environment variables and contribkit's separate credential handling.Breaking changes: Node.js now requires
^22.18.0 || ^24.11.0 || >=26.0.0. Direct callers ofgenSvgImageandgenerateBadgemust supply a crop ID; built-in renderers allocate these throughSvgComposer.getNextCropId().Local validation: 8 Jest tests and 52 Vitest tests pass, as do ESLint, TypeScript checking, production JS/declaration builds, packaged CLI/export smoke checks, and
npm publish --dry-run --tag upstream-sync-validation. The explicit dry-run tag accommodates the repository's unreleased0.0.0package version.Published through Git as merge
8a9eeca08aadb219a55adc9a74ccf99e3ea20978with subjectchore: merge upstream tag 'v18.0.0'. Its first parent is downstream base3a4e0fff1dbb94e9dc7dfba229d5d2b4775687b8, its second parent is upstream tag commit14d0ea2d8043d893483d12dff13eeacaf0059456, and its tree0527b05c8191458f4798f4f55fc8698140814fbfexactly matches green PR headb6f427ee7f594d686de4c50bdb96051563c668d4. Remote master and upstream ancestry are verified. The organization administrator explicitly authorized and configured the repository-rule bypass. This validation PR is closed because the tested tree has been integrated through Git; Post-push master CI passed: the CI-Node workflow (including build and draft-release creation), CodeQL actions and JavaScript analyses, and SonarCloud Code Analysis all succeeded. The master Sonar quality gate is OK with zero open issues.Screenshot
Issues Fixed or Closed
Roadmap Issues
Type of Change
Checklist
AI Usage
See our AI usage policy.