Skip to content

Decouple GitHub-release assembly from per-target builds#728

Open
ptr727 wants to merge 2 commits into
developfrom
feature/727-decouple-release-assets
Open

Decouple GitHub-release assembly from per-target builds#728
ptr727 wants to merge 2 commits into
developfrom
feature/727-decouple-release-assets

Conversation

@ptr727

@ptr727 ptr727 commented Jun 5, 2026

Copy link
Copy Markdown
Owner

Re-converge with the template change in ptr727/ProjectTemplate#108 (shipped in ProjectTemplate#109).

What

github-release collected the release file by referencing build-executable by its artifact-id output. This switches to the template's release-asset-<branch>-* artifact convention: the executable leaf task uploads release-asset-<branch>-executable, and github-release collects assets by pattern (release-asset-<branch>-*, merge-multiple) instead of naming a build job.

Why

Keeps the release orchestration identical to upstream so it stays in sync, and decouples it from the specific build targets. No behavior change — the same executable .7z lands on the GitHub release.

Changes

  • build-executable-task.yml: rename the release artifact to release-asset-<branch>-executable; drop the now-unused artifact-id outputs.
  • build-release-task.yml: github-release collects assets via pattern download.

actionlint (Docker) is clean on the changed files.

Fixes #727

Mirror ProjectTemplate #108/#109: collect release assets by the
release-asset-<branch>-* artifact convention instead of referencing the
build-executable job by artifact-id, so github-release stays target-
agnostic. Rename the executable release artifact and drop its now-unused
artifact-id outputs.

Fixes #727
Copilot AI review requested due to automatic review settings June 5, 2026 02:24

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Pull request overview

This PR updates the release workflow to decouple GitHub Release asset collection from specific build jobs, aligning PlexCleaner’s workflows with the upstream ProjectTemplate convention. Instead of downloading artifacts via per-job artifact-id outputs, the release job now downloads all artifacts that match the release-asset-<branch>-* naming pattern.

Changes:

  • Switch build-release-task.yml GitHub Release asset download to pattern: release-asset-${{ inputs.branch }}-* with merge-multiple: true.
  • Rename the executable release artifact in build-executable-task.yml to release-asset-${{ inputs.branch }}-executable.
  • Remove now-unused artifact-id workflow outputs from build-executable-task.yml.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
.github/workflows/build-release-task.yml Updates GitHub Release job to download release assets by pattern (release-asset-<branch>-*) instead of referencing a specific build job’s artifact output.
.github/workflows/build-executable-task.yml Renames the uploaded executable release artifact to the new release-asset-<branch>-executable convention and drops the unused artifact-id outputs.

Comment thread .github/workflows/build-release-task.yml Outdated
PlexCleaner pins fail_on_unmatched_files: true over ./Publish/*, so an
empty ./Publish fails the release step — the prior comment's 'file-less
release still works' claim (copied from the template, which leaves the
flag default-false) was inaccurate here.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.

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