chore: sync upstream PR #7301 - Don't process response body for http status 204 (no content)

[riderx]

Upstream PR Sync

This PR syncs changes from an external contributor's PR on the official Capacitor repository.

Original PR

• PR: #7301
• Title: Don't process response body for http status 204 (no content)
• Author: @jwltr

Automation

• CI will run automatically
• Claude Code will review for security/breaking changes
• If approved, this PR will be auto-merged

---

Synced from upstream by Capacitor+ Bot

[coderabbitai]

Warning

Rate limit exceeded

@riderx has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 24 minutes and 35 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 270d700 and e997faa.

📒 Files selected for processing (1)

• core/src/core-plugins.ts (1 hunks)

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch sync/upstream-pr-7301

---

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

[riderx]

Thanks for the submission.
This PR has no file changes and is older than 1 day, so it is being closed.
Please reopen with concrete code changes when ready.

[riderx]

Thanks for your PR. Security-related changes should be coordinated through a private advisory before opening a public PR.\n\nPlease open a private advisory here:\n- https://capgo.app/fr/security/\n- https://github.com/Cap-go/capgo/security/advisories/new\n\nI am closing this PR for now.

[riderx]

This PR appears to describe a security-related issue publicly. For security changes, please use a private advisory before opening a public PR. See https://capgo.app/fr/security/ and https://github.com/Cap-go/capgo/security/advisories/new.

[riderx]

Thanks for your submission. Security-sensitive public PRs should be disclosed via private advisory first.

• https://capgo.app/fr/security/
• https://github.com/Cap-go/capgo/security/advisories/new