feat: Added support for YunExpress tracking numbers.

[bramp]

Summary by CodeRabbit

• New Features

  • Added YunExpress as a supported courier for package tracking.
  • Recognizes YunExpress 16-digit tracking numbers, including formats with optional spaces.

• Documentation

  • Improved spacing in the courier definition documentation for easier reading.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: e54c0a0a-f384-41ff-87f2-943a3a5b7f87

📥 Commits

Reviewing files that changed from the base of the PR and between 9bae43b and a9dfa9d.

📒 Files selected for processing (1)

• README.md

---

📝 Walkthrough

Walkthrough

Adds a YunExpress courier definition with tracking URL, serial-number pattern, and test numbers. Updates README spacing before the couriers/*.json documentation section.

Changes

YunExpress courier support

Layer / File(s)	Summary
Courier definition and documentation spacing couriers/yunexpress.json, README.md	Adds the YunExpress courier definition with valid and invalid test numbers. Inserts a blank line before the couriers/*.json documentation section.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Suggested reviewers: jkeen

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The pull request title "feat: Added support for YunExpress tracking numbers" directly and clearly reflects the main changes in the changeset. The primary modifications include adding a new YunExpress courier definition file (couriers/yunexpress.json) and updating the README to document this new supported tracking number. The title is concise, specific, and uses clear language without vague terms or noise. A teammate scanning the commit history would immediately understand that YunExpress tracking support was added to the project.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 802d8a5 and 85895e1.

📒 Files selected for processing (2)

• README.md (1 hunks)
• couriers/yunexpress.json (1 hunks)

🔇 Additional comments (3)

couriers/yunexpress.json (2)

13-22: Test numbers validation looks correct.

The test numbers align well with the regex pattern:

• Valid examples have exactly 16 digits (plus YT prefix = 18 total)
• Spaced variant correctly shows optional spaces are handled
• Invalid example with only 15 digits correctly fails the pattern

---

9-12: YunExpress regex follows existing pattern but conflicts with documented requirement—requires developer decision.

The regex indeed lacks a CheckDigit named group, which contradicts the README requirement at line 61. However, this violation is not unique: three other courier files already deployed lack CheckDigit:

• amazon.json
• landmark.json
• lasership.json

Additionally, the README's own tracking number table (lines 14–33) lists many couriers with only SerialNumber, contradicting the stated requirement. No code-level validation was found enforcing this requirement.

Decide whether to:

1. Remove/relax the requirement from README line 61 (reflecting actual codebase reality)
2. Add CheckDigit groups to all four files (yunexpress, amazon, landmark, lasership)
3. Document that CheckDigit is optional for carriers without checksums

README.md (1)

48-48: Formatting change appears reasonable.

The blank line after "## JSON Format" separates the section header from the content, improving readability.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

YunExpress table entry is in the wrong position.

The entry is currently inserted between "UPS Waybill" (line 41) and "USPS 22" (line 43), breaking the alphabetical carrier grouping. YunExpress should be added after all USPS entries (which end at line 45), not in the middle of them.

The carrier order should be: ...UPS Waybill | USPS 20 | USPS 22 | USPS 34v2 | USPS 91 | YunExpress.

Move the YunExpress row to follow the USPS entries. The correct insertion point is after line 45 (USPS 91 entry):

| **USPS**         | USPS 91 (IMpb)            | 25–34  | `420221539101026837331000039521` `9361289878700317633795` | `RoutingApplicationId` `DestinationZip` `ApplicationIdentifier` `SCNC` `ServiceType` `ShipperId` `PackageId` `CheckDigit` |
+| **YunExpress**   | YunExpress                | 18     | `YT2229521272164446`                                      | `SerialNumber`                                                                                                            |

Committable suggestion skipped: line range outside the PR's diff.

🤖 Prompt for AI Agents

In README.md around lines 42 to 45, the YunExpress table row is misplaced
between "UPS Waybill" and "USPS 22"; move the entire YunExpress row (the line
currently at 42) so it appears after the USPS entries (i.e., insert it
immediately after line 45 where the USPS 91 entry ends) to restore correct
alphabetical carrier grouping.

[github-actions]

🎉 This PR is included in version 1.12.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀