chore: remove ignored cargo build config

[ZocoLini]

In this PR I remove the profile.release sections in the crates Cargo.toml. They were not being applied bcs they need to be specified at the workspace level. I didn't write a replacement because the workspace already provides optimized profiles for the swift sdk builds

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have added "!" to the title and described breaking changes in the corresponding section if my code contains any
• I have made corresponding changes to the documentation if needed

For repository code-owners and collaborators only

• I have assigned this pull request to a milestone

Summary by CodeRabbit

• Chores
  • Removed custom release build profile configurations from multiple packages, standardizing release build settings across the project.

[thepastaclaw]

✅ Review complete (commit 7f206c3)

[coderabbitai]

Warning

Review limit reached

@ZocoLini, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 48 minutes and 56 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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 credits.

🚦 How do rate 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 see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: c9b3a30d-0502-47da-ba67-8f89e93ab20b

📥 Commits

Reviewing files that changed from the base of the PR and between 2168be3 and 7f206c3.

📒 Files selected for processing (3)

• packages/rs-sdk-ffi/Cargo.toml
• packages/wasm-dpp/Cargo.toml
• packages/wasm-sdk/Cargo.toml

📝 Walkthrough

Walkthrough

Three crate manifests (packages/rs-sdk-ffi, packages/wasm-dpp, packages/wasm-sdk) each had their [profile.release] section removed. The deleted settings collectively covered lto, opt-level, panic, codegen-units, strip, and debug overrides.

Changes

Release Profile Cleanup

Layer / File(s)	Summary
Remove [profile.release] from three crate manifests packages/rs-sdk-ffi/Cargo.toml, packages/wasm-dpp/Cargo.toml, packages/wasm-sdk/Cargo.toml	Deletes per-crate [profile.release] blocks that individually set lto, opt-level, panic, codegen-units, strip, and debug overrides across all three packages.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

• shumkov
• QuantumExplorer
• llbartekll

Poem

🐇 Hop, hop, away with the bloat!
Three Cargo files shed their coat.
No more lto = "fat" to weigh us down,
opt-level = "z" has left the town.
The workspace now decides our fate —
One profile to rule, centralized and great! 🌟

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: removing cargo build configuration sections from Cargo.toml files across multiple packages.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/ignored-build-config

---

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.}

[thepastaclaw]

Code Review

PR #3948 removes ignored [profile.release] blocks from three non-root workspace member Cargo.toml files (rs-sdk-ffi, wasm-dpp, wasm-sdk). Cargo only honors profiles defined at the workspace root, so these sections were dead config; iOS builds use workspace-level release-ios/dev-ios profiles and wasm builds inject release settings via cargo --config. Both agents and CodeRabbit found no actionable issues.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.18%. Comparing base (48f0cc3) to head (7f206c3).

Additional details and impacted files

@@            Coverage Diff             @@
##           v3.1-dev    #3948    +/-   ##
==========================================
  Coverage     87.17%   87.18%            
==========================================
  Files          2629     2632     +3     
  Lines        327221   327563   +342     
==========================================
+ Hits         285265   285592   +327     
- Misses        41956    41971    +15     

Components	Coverage Δ
dpp	87.70% <ø> (ø)
drive	86.14% <ø> (ø)
drive-abci	89.45% <ø> (ø)
sdk	∅ <ø> (∅)
dapi-client	∅ <ø> (∅)
platform-version	∅ <ø> (∅)
platform-value	92.20% <ø> (ø)
platform-wallet	∅ <ø> (∅)
drive-proof-verifier	49.55% <ø> (ø)

🚀 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.