Skip to content

Release: merge master-next to master (2026-W23)#15791

Closed
rpcme wants to merge 74 commits into
masterfrom
master-next
Closed

Release: merge master-next to master (2026-W23)#15791
rpcme wants to merge 74 commits into
masterfrom
master-next

Conversation

@rpcme

@rpcme rpcme commented Jun 2, 2026

Copy link
Copy Markdown
Member

Weekly Release Merge

Merge master-next into master for the week 23 release.

Key changes since last release (2026-W20, May 12)

Notes

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

meta-aws-maintainer and others added 27 commits May 27, 2026 02:43
While DEBUG_BUILD = "1", QA 32bit-time WARNING on dbg package.
Rebased from #15696 onto current recipe version (0.39.1).

Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
GCC 16.1.0 emits a spurious -Warray-bounds warning on arm64, arm, and
riscv64 when std::mutex is placement-new'd into aligned storage in
MonitoringManager.cpp. This is a known GCC false positive with small
mutex implementations.

Suppress with -Wno-error=array-bounds until upstream fixes GCC 16
compatibility.

This workaround should be reviewed periodically and removed once
upstream aws-sdk-cpp addresses the issue.
- Update SRCREV to v1.43.1 tag (ee17265421b6a165cf2c29a84fe419bf412c2cde)
- Remove mqtt5-pubsub sample recipe (sample removed upstream in v1.41.0)
- Update fleet-provisioning sample path (moved to samples/service_clients/ in v1.40.2)
- Drop 001-fix-dangling-reference-fleet-provisioning.patch (fixed upstream)
- Add FILES for lib64 versioned .so packaging (from PR #15717 by Wenlin Kang)
- Point RDEPENDS ptest to fleet-provisioning sample instead of removed mqtt5-pubsub

Co-authored-by: Wenlin Kang <wenlin.kang@windriver.com>
@rpcme rpcme requested a review from a team as a code owner June 2, 2026 12:10
@rpcme

rpcme commented Jun 2, 2026

Copy link
Copy Markdown
Member Author

Replacing with conflict-resolved PR.

@rpcme rpcme closed this Jun 2, 2026
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.

4 participants