Skip to content

Release: ff-merge wrynose-next → wrynose (2026-W30) - #16450

Closed
rpcme wants to merge 80 commits into
wrynosefrom
wrynose-next
Closed

Release: ff-merge wrynose-next → wrynose (2026-W30)#16450
rpcme wants to merge 80 commits into
wrynosefrom
wrynose-next

Conversation

@rpcme

@rpcme rpcme commented Jul 29, 2026

Copy link
Copy Markdown
Member

Weekly release — fast-forward merge from wrynose-next into wrynose.

meta-aws-maintainer and others added 30 commits June 15, 2026 23:49
(cherry picked from commit bacdbcc)
(cherry picked from commit 18f6767)
(cherry picked from commit 11b5453)
(cherry picked from commit f92903e)
The yocto-check-layer workflow was using Yocto release codenames directly
as BitBake branch names (e.g. -b wrynose), but BitBake uses version
numbers for branches (2.8, 2.16, 2.18, etc).

This caused all wrynose-next PR checks to fail with:
  fatal: Remote branch wrynose not found in upstream origin

Add explicit mapping:
  scarthgap -> 2.8
  whinlatter -> 2.16
  wrynose -> 2.18
  master -> master

Also add retry logic for git clone (matching build-test-recipe.yml)
since git.openembedded.org has intermittent availability issues.
meta-aws-maintainer and others added 29 commits August 3, 2026 11:59
The ci/ gitlink was erroneously introduced by the backporter tool's
git add --all, which staged the meta-aws-ci checkout directory as a
submodule reference without a .gitmodules entry. This causes failures
when recursively updating submodules in super-projects.
@rpcme rpcme closed this Aug 7, 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.

2 participants