Skip to content

Conversation

@Jason2866
Copy link
Collaborator

No description provided.

L-KAYA and others added 26 commits November 28, 2025 11:46
…70 on ESP32-H2

(cherry picked from commit cd33f13)

Co-authored-by: ShenWeilong <[email protected]>
feat(tools): Updated ccache 4.11.2 -> 4.12.1 (v5.3)

See merge request espressif/esp-idf!43569
…bility

(cherry picked from commit 0cf6f50)

Co-authored-by: luoxu <[email protected]>
fix(ble_mesh): add proper memory cleanup in composition data parsing (v5.3)

See merge request espressif/esp-idf!43838
…e/v5.3'

refactor(ble): modularize compressed log scripts for better maintainability (v5.3)

See merge request espressif/esp-idf!43549
Feat/ble mesh log enh v5.3

See merge request espressif/esp-idf!43213
fix(i2s): fix the auto port failure when use simplex on ESP32 (v5.3)

See merge request espressif/esp-idf!43821
(cherry picked from commit dc4e41f)

Co-authored-by: Zhou Xiao <[email protected]>
(cherry picked from commit 6924b8b)

Co-authored-by: Zhou Xiao <[email protected]>
fix(app_trace): prevent possible system crash on uart buffer access (v5.3)

See merge request espressif/esp-idf!43862
fix(bt): fixed crash caused by deinit during A2DP connection initiation(v5.3)

See merge request espressif/esp-idf!43789
fix(bt/controller): Fixed hci connection request event filter bug (v5.3)

See merge request espressif/esp-idf!43877
BLE Log v2 Function Update 251125 (v5.3)

See merge request espressif/esp-idf!43868
…5.3'

change(ble): Updated the maximum number of concurrent connections to 70 on ESP32-H2 (v5.3)

See merge request espressif/esp-idf!43833
@Jason2866 Jason2866 merged commit e4f859b into tasmota:release/v5.3_orig Dec 3, 2025
1 of 2 checks passed
@github-actions
Copy link

github-actions bot commented Dec 3, 2025

Warnings
⚠️ Please consider squashing your 26 commits (simplifying branch history).
⚠️ The Pull Request description is empty. Please provide a detailed description.
⚠️
	The **target branch** for this Pull Request **must be the default branch** of the project (`master`).

	If you would like to add this feature to a different branch, please state this in the PR description and we will consider it.
Messages
📖 This PR seems to be quite large (total lines of code: 8259), you might consider splitting it into smaller PRs

👋 Hello Jason2866, 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 563f462

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.