Auto-backport workflow not copying version-upgrade label to backported PRs

[rpcme]

Problem

The auto-backport workflow is configured to copy all labels from the source PR to backported PRs using copy_labels_pattern: .+, but the version-upgrade label is not being copied.

Example

• Source PR 2026-03-06_01-41-00_master-next_device-defender-for-aws-iot-embedded-sdk #15229 (master-next): Has version-upgrade label ✓
• Backport PR [Backport kirkstone-next] 2026-03-06_01-41-00_master-next_device-defender-for-aws-iot-embedded-sdk #15230 (kirkstone-next): Missing version-upgrade label ✗

Impact

Backported PRs fail the auto-approve workflow because they're missing the required version-upgrade label:

##[error] Label check failed: required any of 'version-upgrade', but found 0.

This blocks automatic approval and merging, requiring manual intervention to:

1. Add the version-upgrade label
2. Manually approve the PR
3. Enable auto-merge

Expected Behavior

When a PR with the version-upgrade label is backported, the backported PRs should automatically receive the same label.

Current Workflow Configuration

.github/workflows/auto-backport.yml:

copy_labels_pattern: .+

This should copy all labels, but it's not working for version-upgrade.

Workaround

Manually add the version-upgrade label to backported PRs.

Related PRs

• 2026-03-06_01-41-00_master-next_device-defender-for-aws-iot-embedded-sdk #15229 (source PR with label)
• [Backport kirkstone-next] 2026-03-06_01-41-00_master-next_device-defender-for-aws-iot-embedded-sdk #15230 (backport PR missing label)

Possible Causes

1. The backport action might be skipping certain labels
2. There might be a timing issue where labels aren't copied
3. The label pattern might not be matching correctly