Skip to content

User/gmileka/test branch - #18696

Draft
George Mileka (gmileka) wants to merge 29 commits into
4.0from
user/gmileka/test-branch
Draft

User/gmileka/test branch#18696
George Mileka (gmileka) wants to merge 29 commits into
4.0from
user/gmileka/test-branch

Conversation

@gmileka

Copy link
Copy Markdown

No description provided.

Copilot AI balanced review requested due to automatic review settings September 2, 2026 18:58
@github-actions

github-actions Bot commented Sep 2, 2026

Copy link
Copy Markdown

Hello, and thank you for opening this pull request! 👋🏼 We appreciate the contribution.

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Commits in this repo will typically be prefixed with fix:, feat:, docs:, chore:, refactor:, test:, or ci: to indicate the type of change being proposed. The linked specification has more details.

Details:

No release type found in pull request title "User/gmileka/test branch". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

The test package is not registered as a component, signing can produce false positives, and generated specs remain stale.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Adds xsign-proxy signing checks to fwupd-related builds and introduces a test package.

Changes:

  • Adds direct pesign-client signing paths.
  • Adds an xsign-proxy test RPM.
  • Refreshes component locks and rendered specs.
File summaries
File Description
base/comps/components.toml Moves fwupd to dedicated configuration.
base/comps/fwupd/fwupd.comp.toml Adds a signing-test overlay.
base/comps/fwupd-efi/fwupd-efi.comp.toml Adds certificate-based EFI signing.
locks/fwupd.lock Refreshes fwupd fingerprint.
locks/fwupd-efi.lock Refreshes fwupd-efi fingerprint.
specs/f/fwupd/fwupd.spec Contains rendered fwupd changes.
specs/f/fwupd-efi/fwupd-efi.spec Contains rendered EFI signing changes.
specs/x/xsign-proxy-test/xsign-proxy-test.spec Adds the test RPM specification.
specs/x/xsign-proxy-test/README Documents the test package.
Review details

Suppressed comments (1)

specs/x/xsign-proxy-test/xsign-proxy-test.spec:87

  • This repeats the unsigned input path, making [ -f "$SIGNED_TEST_FILE" ] true even when no signing branch ran and causing the package to install the unsigned fixture as if it were signed. In the canonical local spec, point this variable at the distinct signed output created in %build.
SIGNED_TEST_FILE="%{_builddir}/%{name}-%{version}/test-file-%{name}-%{version}.txt"
  • Files reviewed: 7/9 changed files
  • Comments generated: 8
  • Review effort level: Balanced

💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread base/comps/fwupd/fwupd.comp.toml Outdated
--sign \
--certificate "cp-459159-pgp" \
--token "unused-token-name" \
--infile "$TEST_FILE" \
Comment thread base/comps/fwupd/fwupd.comp.toml Outdated
@@ -0,0 +1,63 @@
[components.fwupd]

[[components.fwupd.overlays]]
%changelog
## START: Generated by rpmautospec
* Wed Sep 02 2026 azldev <azldev@local> - 1.8-4
- Local changes (uncommitted)
Comment thread specs/f/fwupd/fwupd.spec Outdated
%changelog
## START: Generated by rpmautospec
* Wed Sep 02 2026 azldev <azldev@local> - 2.0.19-3
- Local changes (uncommitted)
@@ -0,0 +1,102 @@
Name: xsign-proxy-test
# Are we running on a secure-boot image?
if [ -x "$PESIGN_CLIENT" ]; then

SIGNED_TEST_FILE="%{_builddir}/%{name}-%{version}/test-file-%{name}-%{version}.txt"
Comment on lines +74 to +75
fi
echo "PASS: pesign sign request completed successfully"
@@ -0,0 +1,102 @@
Name: xsign-proxy-test
Version: 1.0.0
Release: 1%{?dist}
Copilot AI review requested due to automatic review settings September 2, 2026 19:08

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

Signing correctness, missing component registration, and stale rendered changelogs must be addressed.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Review details

Suppressed comments (4)

Previously missed (3) — in code that hasn't changed since the last review.

specs/x/xsign-proxy-test/xsign-proxy-test.spec:3

  • This adds the package only under specs/, which base/project.toml:13 declares as generated rendered output. No component definition or lock exists for xsign-proxy-test, so azldev cannot discover, update, render, or build it, and rendered-spec cleanup can discard it. Add a dedicated local component under base/comps/xsign-proxy-test/, use the repository's %autorelease/%autochangelog convention for new local specs, generate its lock, and re-render the output.
    specs/x/xsign-proxy-test/xsign-proxy-test.spec:37
  • SIGNED_TEST_FILE is identical to TEST_FILE, so it exists before any signing request. As a result, the later existence checks and %install path cannot distinguish a signed result from the original unsigned text, and an unset/unsupported signing type still reports PASS and packages the original file. Use a distinct .signed output consistently here and in %install, and fail when no requested signing mode ran.
    specs/f/fwupd/fwupd.spec:430
  • The generated changelog still says Local changes (uncommitted), so it was rendered before the component commit existed. Repository guidance in .github/copilot-instructions.md:56 requires a post-commit render-and-amend; otherwise Check Rendered Specs will detect drift.

base/comps/fwupd/fwupd.comp.toml:33

  • TEST_FILE is never initialized anywhere in the fwupd spec, so whenever this branch is entered, pesign-client --infile "$TEST_FILE" receives an empty path and the later ls "$TEST_FILE" fails the build. This overlay appears to copy test-package logic into fwupd without creating an input artifact; remove it or define and create the intended artifact before signing.
            --infile "$TEST_FILE" \
  • Files reviewed: 7/9 changed files
  • Comments generated: 2
  • Review effort level: Balanced

Comment on lines +107 to +118
else
%pesign -s -i %{fwup_efi_fn} -o %{fwup_efi_fn}.signed
fi

ls -la "$TEST_FILE"
ls -la "$SIGNED_TEST_FILE"'''

[[components.fwupd-efi.overlays]]
description = "Remove cleanup for the eliminated intermediate signed EFI file"
type = "spec-search-replace"
section = "%install"
regex = '^rm -vf %\{fwup_efi_fn\}\.tmp$'
%changelog
## START: Generated by rpmautospec
* Wed Sep 02 2026 azldev <azldev@local> - 1.8-5
- Local changes (uncommitted)
Copilot AI review requested due to automatic review settings September 3, 2026 00:18

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 Needs a closer look

The test component is unregistered, can report success without signing, and the fwupd-efi rendered output is stale.

Review details

Suppressed comments (6)

Previously missed (2) — in code that hasn't changed since the last review.

specs/f/fwupd-efi/fwupd-efi.spec:132

  • gwupd appears to be a typo for fwupd; no gwupd component or other reference exists in the repository. Correct the source commit message and re-render rather than editing this generated changelog directly.
    specs/x/xsign-proxy-test/xsign-proxy-test.spec:43
  • The option name is misspelled in both examples; pesign-client uses --certificate.

specs/x/xsign-proxy-test/xsign-proxy-test.spec:1

  • This file is being added only under specs/, but that tree is generated output (.github/copilot-instructions.md:28-43) and there is no [components.xsign-proxy-test] definition or lock in the repository. As a result, azldev cannot render/build this package, and a render-all with --clean-stale will prune the directory. Add it as a local component under base/comps/xsign-proxy-test/, generate its lock, and then commit the rendered output.
Name:           xsign-proxy-test

specs/x/xsign-proxy-test/xsign-proxy-test.spec:75

  • An empty or unrecognized SIGULDRY_PESIGN_BRIDGE_SIGNING_TYPES value skips every pesign-client branch, but execution still reports PASS. That lets this communication test succeed without ever contacting xsign-proxy; fail explicitly when no supported signing type is selected.
    echo "PASS: pesign sign request completed successfully"

specs/x/xsign-proxy-test/xsign-proxy-test.spec:3

  • This newly authored local spec uses a static release and handwritten changelog instead of the repository's %autorelease/%autochangelog convention (see base/comps/telegraf/telegraf.comp.toml:7-9 and telegraf.spec:24-25). Convert both macros and set the new component's release calculation to autorelease so azldev can keep release history synchronized.
Release:        1%{?dist}

specs/f/fwupd-efi/fwupd-efi.spec:129

  • The generated changelog still contains Local changes (uncommitted), proving this spec was rendered before the component commit existed. Per .github/copilot-instructions.md:54-60, re-render after committing and amend the result; otherwise the rendered-spec CI check will regenerate different release/changelog content.
* Wed Sep 02 2026 azldev <azldev@local> - 1.8-5
- Local changes (uncommitted)
  • Files reviewed: 4/5 changed files
  • Comments generated: 0 new
  • Review effort level: Balanced

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