Skip to content

aws-greengrass-component-sdk: remove stale v1.0.1 files from master - #15576

Merged
rpcme merged 1 commit into
aws4embeddedlinux:masterfrom
rpcme:fix/cleanup-stale-sdk-files
Apr 27, 2026
Merged

aws-greengrass-component-sdk: remove stale v1.0.1 files from master#15576
rpcme merged 1 commit into
aws4embeddedlinux:masterfrom
rpcme:fix/cleanup-stale-sdk-files

Conversation

@rpcme

@rpcme rpcme commented Apr 27, 2026

Copy link
Copy Markdown
Member

Problem

The release PR #15575 (master-next → master) fails because _1.0.1.bb on master still references patches that were removed on master-next during the v1.0.2 upgrade.

Git cannot resolve this during merge because the rename chain diverged due to a prior force-push to master (now prevented by branch protection).

Fix

Explicitly delete the stale files from master:

  • aws-greengrass-component-sdk_1.0.1.bb (superseded by _1.0.2.bb on master-next)
  • 0001-Add-timespec-blocklist-and-portable-struct-for-cross.patch (upstreamed in v1.0.2)
  • 0002-Fix-timespec-types-for-32-bit-platforms.patch (upstreamed in v1.0.2)

Process

  1. Merge this PR into master
  2. Then merge release PR Release: merge master-next to master (2026-04-27) #15575 (master-next → master) cleanly

This is a one-time cleanup of damage from the prior force-push.

These files were superseded by the v1.0.2 upgrade on master-next but
remain on master due to divergent history from a prior force-push.
Remove them so the master-next to master release merge is clean.
@rpcme
rpcme requested a review from a team as a code owner April 27, 2026 14:58
@rpcme
rpcme merged commit c76e45c into aws4embeddedlinux:master Apr 27, 2026
6 checks passed
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.

1 participant