feat: add USDC/ethereum-lukso warp route

[CJ42]

Summary by CodeRabbit

Release Notes

• New Features

  • Added USDC warp route support enabling cross-chain token bridging between Ethereum and Lukso.

• Chores

  • Added changeset entry for @hyperlane-xyz/registry minor release.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR adds a changeset entry for a minor version bump of @hyperlane-xyz/registry and introduces USDC warp route configuration files that establish cross-chain bridging between Ethereum and Lukso networks, including deployment parameters and token specifications.

Changes

Cohort / File(s)	Summary
Changeset Metadata .changeset/tough-meals-rhyme.md	Documents minor version bump for @hyperlane-xyz/registry with the new USDC/ethereum-lukso warp route feature.
USDC/Lukso Warp Route Configuration deployments/warp_routes/USDC/lukso-config.yaml, deployments/warp_routes/USDC/lukso-deploy.yaml	Defines token configurations and deployment parameters for USDC bridging between Ethereum (collateral) and Lukso (synthetic), specifying addresses, decimals, proxy admin settings, and cross-chain connection mappings.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• feat: extend USDC/matchain #1099 — Also adds USDC warp-route configuration and registry changeset entries, extending cross-chain USDC bridging infrastructure.

Suggested reviewers

• Xaroz
• paulbalaji

Poem

🌉 A bridge of tokens spans the way,
From Ethereum to Lukso's day,
USDC flows through layers deep,
A warp route strong, a promise to keep. 💫

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request description is entirely empty, missing all required sections from the template including Description, Backward compatibility, and Testing information.	Add a description covering the summary of changes, backward compatibility assessment, and testing validation with Hyperlane tooling as specified in the template.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'feat: add USDC/ethereum-lukso warp route' accurately describes the main change: adding a new USDC warp route configuration between Ethereum and Lukso networks.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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 and usage tips.}

[coderabbitai]

Actionable comments posted: 3

🤖 Fix all issues with AI agents

In `@deployments/warp_routes/USDC/mainnet-lukso-config.yaml`:
- Around line 1-19: The warp route ID/filename is inconsistent: the changeset
uses the label "USDC/ethereum-lukso" but the file is named
mainnet-lukso-config.yaml; rename the file to follow the {SYMBOL}/{label}
convention by changing the filename to ethereum-lukso-config.yaml (so the label
is the chain names joined by a hyphen) and ensure the token entries (symbol:
USDC, chainName: lukso and chainName: ethereum) remain unchanged inside the
file.

In `@deployments/warp_routes/USDC/mainnet-lukso-deploy.yaml`:
- Around line 9-18: The YAML keys under the lukso mapping are not alphabetically
ordered; reorder the top-level keys for the lukso block (decimals, isNft, name,
owner, proxyAdmin, symbol, type) into alphabetical order and also alphabetize
the nested proxyAdmin keys (address, owner) so the entire lukso mapping follows
the project's "YAML files must have keys sorted alphabetically" guideline;
update the lukso mapping accordingly while preserving all values.
- Around line 1-8: The YAML keys under the ethereum mapping are out of
alphabetical order; reorder the top-level keys (owner, proxyAdmin, token, type,
decimals) so they are alphabetically sorted and also sort nested keys under
proxyAdmin (address, owner) alphabetically; update the ethereum block in
mainnet-lukso-deploy.yaml so keys appear in strict alphabetical order while
preserving all existing values.