chore(release): publish 3.0.1

[Copilot]

This PR bumps the library version from 3.0.0 to 3.0.1 in preparation for a patch release.

Changes Made

• Updated version field in root package.json from "3.0.0" to "3.0.1"
• No other files modified (example package.json remains at version 1.0.0)
• No CHANGELOG updates as requested by maintainer

Context

This is a lightweight preparation PR for an upcoming patch release. The current 3.0.0 version has already been published to npm, and this version bump prepares the repository for the next patch release in the 3.0.x series.

After merging, the maintainer can proceed with:

• Tagging the retroactive v3.0.0 commit (if needed)
• Running the release process to tag and publish v3.0.1

The change is minimal and surgical - affecting only the version metadata without any functional changes to the library code.

Original prompt

Goal

Prepare a pull request that bumps the library version from 3.0.0 to 3.0.1 in preparation for a patch release. The maintainer has explicitly stated there is "No need for changelog" for this prep PR.

Context

• Repository: wuba/react-native-echarts
• Current package.json version: 3.0.0 (already published to npm as 3.0.0 but Git tag/release may be missing).
• We are creating a lightweight PR that only updates the version field in the root package.json to 3.0.1. No CHANGELOG or other doc updates requested.
• The example workspace package (example/package.json) remains unchanged (version 1.0.0) unless there is a policy to sync, which has not been indicated by the maintainer.

Required Changes

1. Edit root package.json:
   • Change "version": "3.0.0" -> "version": "3.0.1".
2. Do not modify any other fields.
3. No CHANGELOG addition (per maintainer instruction).
4. Provide a concise commit message.

Commit Message Suggestion

chore(release): prepare 3.0.1

Post-merge / Maintainer Follow-up (informational, not part of code changes)

• (Optional) Tag the retroactive v3.0.0 commit if not yet tagged.
• Run release process (e.g., release-it) or manually tag & publish v3.0.1 after merging.

Acceptance Criteria

• Pull request shows only the single-line version bump in root package.json.
• CI (if present) should pass without additional adjustments.

Please implement only the specified version bump.

*This pull request was created as a result of the following prompt from Copilot chat.* > ## Goal > Prepare a pull request that bumps the library version from 3.0.0 to 3.0.1 in preparation for a patch release. The maintainer has explicitly stated there is "No need for changelog" for this prep PR. > > ## Context > - Repository: wuba/react-native-echarts > - Current package.json version: 3.0.0 (already published to npm as 3.0.0 but Git tag/release may be missing). > - We are creating a lightweight PR that only updates the version field in the root package.json to 3.0.1. No CHANGELOG or other doc updates requested. > - The example workspace package (example/package.json) remains unchanged (version 1.0.0) unless there is a policy to sync, which has not been indicated by the maintainer. > > ## Required Changes > 1. Edit root package.json: > - Change "version": "3.0.0" -> "version": "3.0.1". > 2. Do not modify any other fields. > 3. No CHANGELOG addition (per maintainer instruction). > 4. Provide a concise commit message. > > ## Commit Message Suggestion > chore(release): prepare 3.0.1 > > ## Post-merge / Maintainer Follow-up (informational, not part of code changes) > - (Optional) Tag the retroactive v3.0.0 commit if not yet tagged. > - Run release process (e.g., release-it) or manually tag & publish v3.0.1 after merging. > > ## Acceptance Criteria > - Pull request shows only the single-line version bump in root package.json. > - CI (if present) should pass without additional adjustments. > > Please implement only the specified version bump.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.