Skip to content

chore: standardize repository maintenance - #48

Merged
afc163 merged 15 commits into
mainfrom
codex/standardize-rc-infra
Jul 3, 2026
Merged

chore: standardize repository maintenance#48
afc163 merged 15 commits into
mainfrom
codex/standardize-rc-infra

Conversation

@afc163

@afc163 afc163 commented Jul 1, 2026

Copy link
Copy Markdown
Member

Summary

  • Refresh README and README.zh-CN with centered heading, badges, Ant Design ecosystem branding, install, usage, development, release, and license sections.
  • Align Funding, grouped Dependabot updates, CodeQL, React Doctor, reusable test workflow, Surge preview, and Vercel preview configuration.
  • Align release documentation and scripts with @rc-component/np; remove legacy Now configuration where present.

Refs ant-design/ant-design#58514

Test

  • npm run lint\n- npm run tsc\n- npm run compile\n- npm run build\n- npm test was blocked locally because Cypress binary download failed in this environment.\n- git diff --check
  • JSON parse check for package/config files
  • README consistency scan

@coderabbitai

coderabbitai Bot commented Jul 1, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@afc163, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: f9f0bded-4dce-4ff7-ad90-db7c27dabe01

📥 Commits

Reviewing files that changed from the base of the PR and between 8726b8b and e170394.

📒 Files selected for processing (22)
  • .eslintrc.js
  • .github/FUNDING.yml
  • .github/dependabot.yml
  • .github/workflows/ci.yml
  • .github/workflows/codeql.yml
  • .github/workflows/react-doctor.yml
  • .github/workflows/surge-preview.yml
  • .github/workflows/test.yml
  • README.md
  • README.zh-CN.md
  • app/body-overflow/page.tsx
  • app/fail/page.tsx
  • app/shadow-dom/page.tsx
  • cypress.config.js
  • cypress.config.ts
  • docs/shadow-dom.tsx
  • eslint.config.mjs
  • global.d.ts
  • now.json
  • package.json
  • tsconfig.json
  • vercel.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch codex/standardize-rc-infra

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions

github-actions Bot commented Jul 1, 2026

Copy link
Copy Markdown

React Doctor found no new issues. 🎉

Reviewed by React Doctor for commit e170394.

@codecov

codecov Bot commented Jul 1, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 57.49%. Comparing base (8726b8b) to head (28e22e1).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #48   +/-   ##
=======================================
  Coverage   57.49%   57.49%           
=======================================
  Files          12       12           
  Lines         527      527           
  Branches      153      153           
=======================================
  Hits          303      303           
  Misses        162      162           
  Partials       62       62           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the repository's configuration, documentation, and dependencies. Key changes include adding a funding configuration, expanding Dependabot updates, rewriting the English README, adding a Chinese README, migrating docs/shadow-dom.tsx to React 18's createRoot, updating package.json scripts and dependencies, and adding a Vercel configuration. Feedback focuses on ensuring consistency by using pnpm instead of npm across the READMEs, package.json, and vercel.json. Additionally, it is recommended to clean up the redundant API header in the README and properly unmount the React root in docs/shadow-dom.tsx to prevent memory leaks.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Comment thread README.md
Comment thread README.zh-CN.md
Comment thread package.json
Comment thread vercel.json
Comment thread README.md Outdated
Comment thread docs/shadow-dom.tsx Outdated
@socket-security

socket-security Bot commented Jul 1, 2026

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm es-abstract is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: ?npm/eslint-plugin-react@7.37.5npm/es-abstract@1.24.2

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/es-abstract@1.24.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm eslint-plugin-react is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: package.jsonnpm/eslint-plugin-react@7.37.5

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/eslint-plugin-react@7.37.5. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm webpack is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: package.jsonnpm/webpack@5.108.3

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/webpack@5.108.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm yargs is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: ?npm/eslint-plugin-jest@29.15.4npm/dumi@2.4.7npm/@rc-component/np@1.0.4npm/@umijs/fabric@4.0.1npm/yargs@17.7.3

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/yargs@17.7.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

Copilot AI review requested due to automatic review settings July 2, 2026 03:54

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR standardizes repository maintenance and project metadata across docs, tooling, CI, and deployment previews for @rc-component/dom-align, aligning it with the Ant Design / rc-component ecosystem patterns (release flow, GitHub workflows, Dependabot, etc.).

Changes:

  • Refresh English/Chinese READMEs and adjust package metadata/scripts (including switching release to rc-np).
  • Replace legacy lint config with ESLint flat config, adjust TypeScript config, and modernize example/demo code for React 18+ APIs.
  • Align GitHub maintenance automation (test workflow reuse, CodeQL, Dependabot grouping, Surge preview, funding) and replace legacy deployment config (now.jsonvercel.json).

Reviewed changes

Copilot reviewed 20 out of 22 changed files in this pull request and generated 2 comments.

Show a summary per file
File Description
vercel.json Adds Vercel build/output configuration for the docs site.
tsconfig.json Updates TS compiler settings and program include patterns.
README.zh-CN.md Adds refreshed Simplified Chinese README with standardized sections.
README.md Rewrites README layout/sections and updates commands/release docs.
package.json Updates package metadata, scripts, and dev tooling dependencies.
now.json Removes legacy Now/Vercel v2 config.
global.d.ts Adds a global *.css module declaration.
eslint.config.mjs Introduces ESLint flat-config setup (React/TS/Jest rules).
docs/shadow-dom.tsx Modernizes shadow DOM demo (refs + createRoot + cleanup).
cypress.config.ts Removes TS Cypress config.
cypress.config.js Adds JS Cypress config with explicit webpack+babel devServer setup.
app/shadow-dom/page.tsx Improves typing and non-null assertions for refs in demo page.
app/fail/page.tsx Improves typing and non-null assertions for refs in demo page.
app/body-overflow/page.tsx Improves typing for refs/timers and non-null assertions.
.github/workflows/test.yml Adds standardized reusable test workflow invocation.
.github/workflows/surge-preview.yml Adds Surge preview workflow gated by SURGE_TOKEN.
.github/workflows/react-doctor.yml Adds React Doctor workflow for PR/push analysis.
.github/workflows/codeql.yml Adds CodeQL scanning workflow.
.github/workflows/ci.yml Removes legacy CI workflow.
.github/FUNDING.yml Adds funding links for GitHub/OpenCollective.
.github/dependabot.yml Standardizes Dependabot schedules and groups updates.
.eslintrc.js Removes legacy ESLint config in favor of flat config.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread eslint.config.mjs
Comment thread README.md Outdated
@afc163
afc163 merged commit 1cab1bf into main Jul 3, 2026
9 checks passed
@afc163
afc163 deleted the codex/standardize-rc-infra branch July 3, 2026 12:30
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.

2 participants