Is your feature request related to a problem? Please describe.
The build-and-release action as of v0.10.1 pushes container images, and uploads DEBs and RPMs into the GitHub Actions Run object. Completing the release requires a manual stage of downloading those files, and uploading to a Release.
Describe the solution you'd like
The build-and-release action should publish DEBs and RPMs to a Release when not performing a release dry run. This would be compatible with how the action handles containers (pushes them to the registry where they are available to users immediately).
Describe alternatives you've considered
GitHub Actions had previously supplied an action to upload a release object in repo actions/upload-release-asset.
Is your feature request related to a problem? Please describe.
The build-and-release action as of v0.10.1 pushes container images, and uploads DEBs and RPMs into the GitHub Actions Run object. Completing the release requires a manual stage of downloading those files, and uploading to a Release.
Describe the solution you'd like
The build-and-release action should publish DEBs and RPMs to a Release when not performing a release dry run. This would be compatible with how the action handles containers (pushes them to the registry where they are available to users immediately).
Describe alternatives you've considered
GitHub Actions had previously supplied an action to upload a release object in repo actions/upload-release-asset.
However that repo has been archived and redirects users to softprops/action-gh-release , which I propose we use. There are examples of how to upload release assets.
I suggest we continue to upload the DEBs and RPMs to the Run object like we do today, and add the Release upload when not in dry-run if possible.
Additional context
No response