Skip to content

Modify release asset preparation in workflow#8

Merged
tomassrnka merged 1 commit into
mainfrom
2025-11-25-Fix-release-workflow-for-multi-kernel-version
Nov 25, 2025
Merged

Modify release asset preparation in workflow#8
tomassrnka merged 1 commit into
mainfrom
2025-11-25-Fix-release-workflow-for-multi-kernel-version

Conversation

@tomassrnka
Copy link
Copy Markdown
Member

@tomassrnka tomassrnka commented Nov 25, 2025

Updated the workflow to prepare release assets by copying vmlinux binaries to a new directory before uploading.


Note

Collects vmlinux binaries into release-assets and uploads those files instead of the raw builds directory.

  • CI workflow (.github/workflows/fc-kernels.yml):
    • Add step to assemble release assets: copy each vmlinux.bin from ./builds/*/ into release-assets/ as vmlinux-<variant>.bin.
    • Update release upload to target ./release-assets/* instead of ./builds/**.

Written by Cursor Bugbot for commit bdad4fa. This will update automatically on new commits. Configure here.

Updated the workflow to prepare release assets by copying vmlinux binaries to a new directory before uploading.
@jakubno
Copy link
Copy Markdown
Member

jakubno commented Nov 25, 2025

Do you know why it worked before and now it doesn't and how does this fixes the issue?

@tomassrnka
Copy link
Copy Markdown
Member Author

Has there ever been 2 kernel versions in parallel? Cause the current code fails as both builds have "vmlinux" as a result..

@tomassrnka tomassrnka merged commit b112d8a into main Nov 25, 2025
2 checks passed
@ValentaTomas ValentaTomas deleted the 2025-11-25-Fix-release-workflow-for-multi-kernel-version branch February 18, 2026 00:57
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