V5.4 (IDFGH-14430)

[Gui71]

Description

Related

Testing

---

Checklist

Before submitting a Pull Request, please ensure the following:

• 🚨 This PR does not introduce breaking changes.
• All CI checks (GH Actions) pass.
• Documentation is updated as needed.
• Tests are updated or added as necessary.
• Code is well-commented, especially in complex areas.
• Git history is clean — commits are squashed to the minimum necessary.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
3 out of 22 committers have signed the CLA.

✅ AlexBethel
✅ ESPAbhinav
✅ hfudev
❌ ESP-Marius
❌ rahult-github
❌ chshu
❌ kumekay
❌ songruo
❌ weiyuhannnn
❌ Isl2017
❌ suda-morris
❌ Jiang Jiang Jian
❌ dobairoland
❌ erhankur
❌ esp-cjh
❌ espressif-bot
❌ zwx1995esp
❌ Astha-cpu
❌ hrushikesh430
❌ mahavirj
❌ Gui71
❌ L-KAYA

---

Jiang Jiang Jian seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[github-actions]

	Warnings
⚠️	Some issues found for the commit messages in this PR: the commit message "Atualização dos componentes de Bluetooth, Wi-Fi e outras dependências": summary looks empty type/action looks empty the commit message "Merge branch 'fix/coredump-gcc-analyzer-warnings_v5.4' into 'release/v5.4'": probably contains Jira ticket reference (GCC-14). Please remove Jira tickets from commit messages. the commit message "Update slave.c to fix the mode": body's lines must not be longer than 100 characters summary looks empty type/action looks empty the commit message "fix(ble): fixed that the resolvable private address does not change when light sleep is enabled": summary appears to be too long Please fix these commit messages - here are some basic tips: follow Conventional Commits style correct format of commit message should be: <type/action>(<scope/component>): <summary>, for example fix(esp32): Fixed startup timeout issue allowed types are: change,ci,docs,feat,fix,refactor,remove,revert,test sufficiently descriptive message summary should be between 20 to 72 characters and start with upper case letter avoid Jira references in commit messages (unavailable/irrelevant for our customers) TIP: Install pre-commit hooks and run this check when committing (uses the Conventional Precommit Linter).
⚠️	Please consider squashing your 250 commits (simplifying branch history).

	Messages
📖	This PR seems to be quite large (total lines of code: 349883), you might consider splitting it into smaller PRs

👋 Hello Gui71, we appreciate your contribution to this project!

---

📘 Please review the project's Contributions Guide for key guidelines on code, documentation, testing, and more.

---

🖊️ Please also make sure you have read and signed the Contributor License Agreement for this project.

---

Click to see more instructions ...

This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- Resolve all warnings (⚠️ ) before requesting a review from human reviewers - they will appreciate it.
- Addressing info messages (📖) is strongly recommended; they're less critical but valuable.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...

We do welcome contributions in the form of bug reports, feature requests and pull requests via this public GitHub repository.

This GitHub project is public mirror of our internal git repository

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved, we synchronize it into our internal git repository.
4. In the internal git repository we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
5. If the change is approved and passes the tests it is merged into the default branch.
5. On next sync from the internal git repository merged change will appear in this public GitHub repository.

Generated by 🚫 dangerJS against dfc5cc4

[Alvin1Zhang]

Thanks for contribution, what are you planning to fix? Thanks.

[Alvin1Zhang]

Thanks for reporting, feel free to reopen.