Release: merge master-next to master (2026-04-27)#15575
Closed
rpcme wants to merge 46 commits into
Closed
Conversation
- auto-backport: remove kirkstone-next target - build-test-all-branches: remove kirkstone/kirkstone-next - ff-merge: clean up to only active branches (master, scarthgap, whinlatter) Kirkstone (Yocto 4.0 LTS) reached EOL April 2026. Also removed dunfell, gatesgarth, hardknott, honister, zeus, langdale, mickledore, nanbield, styhead, and walnascar from ff-merge defaults as all are EOL. Signed-off-by: Richard Elberger <elberger@amazon.com>
SDK recipe: - Remove patch 0003 (cdylib + panic_handler) — upstream uses rlib-only, cdylib caused duplicate panic_impl conflicts with std consumers - Switch BUILD_SHARED_LIBS=OFF (matches upstream static-only model) - Remove libgg_sdk.so install (no longer produced) C++ helloworld: - Remove stale #include <gg/types.hpp> (doesn't exist in v1.0.1) Rust helloworld: - Should now work — rlib no longer contains panic_handler Components are self-contained static binaries per upstream design. The SDK is a build-time dependency only. Fixes #15475 Signed-off-by: Richard Elberger <elberger@amazon.com>
Make sample binary compilation opt-in via PACKAGECONFIG[samples]. Default is off — users enable with: PACKAGECONFIG:append:pn-aws-greengrass-component-sdk = " samples" When enabled: - Builds C samples (CMake BUILD_SAMPLES=ON) - Builds C++ samples (via BUILD_CPP + BUILD_SAMPLES) - Builds Rust examples (cargo --examples) - Installs sample binaries to /usr/bin/ - Installs component recipe JSONs to /usr/share/greengrass/component-recipes/ - Packages as aws-greengrass-component-sdk-samples The component recipe JSONs serve as deployment reference templates that users can customize with their S3 bucket and thing group. NOTE: Yocto SDK (populate_sdk) integration needs verification. Signed-off-by: Richard Elberger <elberger@amazon.com>
The 5 standalone helloworld recipes (bash, c, cpp, python, rust) are superseded by the upstream samples now built and packaged by the aws-greengrass-component-sdk recipe via PACKAGECONFIG[samples]. The upstream SDK samples are more comprehensive (40 samples covering all 13 IPC operations in C, C++, and Rust) and are maintained by the SDK upstream. The helloworld-rust recipe also had a panic_handler conflict with the SDK's no_std rlib that blocked all workflow-only PRs (#15475). Users who want sample components should use: IMAGE_INSTALL:append = " aws-greengrass-component-sdk-samples" The README in recipes-sdk/aws-greengrass-component-sdk/ documents how to write custom component recipes. Signed-off-by: Richard Elberger <elberger@amazon.com>
…lows cve-check.bbclass was removed from OE-core master (2026-03-31, commit 00de455). Replace with sbom-cve-check-recipe which is the official successor. Changes to both pr-cve-check.yml and nightly-cve-check.yml: - INHERIT: cve-check → create-spdx-3.0 sbom-cve-check-recipe - Task: cve_check → sbom_cve_check_recipe - Output: collect .sbom-cve-check.yocto.json files (same format as old cve-summary.json via yocto-cve-check-manifest export) - Re-enable PR trigger on master-next Fixes #15461 Signed-off-by: Richard Elberger <elberger@amazon.com>
The pr-cve-check workflow was running CVE checks against every .bb recipe in the layer on every PR, causing very long run times. Add a 'changed' job (mirroring build-test-recipe pattern) that detects which recipes were modified in the PR, then only CVE-check those. Skip the CVE check entirely if no recipe files changed.
The automated version upgrade (PR #15416) updated the recipe contents to version 1.0.1 but did not rename the file from _0.4.bb to _1.0.1.bb. Rename the file and remove the explicit PV assignment since the version is now derived from the filename per Yocto convention. Reported-by: ChenQi1989 <https://github.com/ChenQi1989>
…on.inc
This line ${GG_ROOT}/plugins = "${GG_ROOT}/plugins" should be changed to
GG_PLUGINS = "${GG_ROOT}/plugins".
Signed-off-by: Xiaozhan Li <xiaozhan.li.cn@windriver.com>
In addition to the update, fixes the bindgen clang args and removes unnecessary patches.
Replace the Docker-based label checker (which requires REVIEWER_TOKEN and fails with 401 on fork PRs) with a simple gh API call using the default GITHUB_TOKEN. Skip approve/merge steps if the label is not present instead of failing the workflow. This prevents red X on non-bot PRs.
Add Releases and Pinning section with examples for kas.yml and git submodule usage. Add supported branches table with EOL dates. Remove reference to kirkstone (EOL April 2026). Fixes #15476
Remove kirkstone from BitBake version mapping comment. Rulesets updated separately: - Removed kirkstone-next from -next staging branches ruleset - Deleted kirkstone-next specific ruleset Partial fix for #15552
The COMPATIBLE_MACHINE filter had three bugs causing false CI failures: 1. Only recognized "null" as a blocking default, but amazon-cloudwatch-agent uses "(^$)" which also means "no machine matches" 2. The qemuarm override check only looked for armv7a/armv7ve but not :arm, missing recipes that use the base arm override 3. The explicit arch-specific null check only covered qemuarm and qemuriscv64, missing qemuarm64 and qemux86-64 Also removes corretto-*/firecracker-bin/jailer-bin from THINGS_TO_EXCLUDE since the filter now handles them properly via COMPATIBLE_MACHINE. Proven locally against all recipes for all four qemu machines. Fixes #15547
Member
Author
|
Closing — master now has the stale file cleanup from #15576. Creating fresh release PR. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Weekly release: master-next → master
Recipe Updates
Bug Fixes
Infrastructure & CI