Skip to content

Attach the installers from where they are downloaded - #42

Merged
Nelsar merged 1 commit into
mainfrom
fix-installers-attach
Oct 23, 2026
Merged

Nelsar merged 1 commit into
mainfrom
fix-installers-attach

Conversation

@n-turkpenbay

@n-turkpenbay n-turkpenbay commented Oct 23, 2026 •

Copy link
Copy Markdown
Collaborator

The v0.3.0 release has no installers attached. The Installers run built both MSIs and installed, upgraded and removed the x64 one, then the attach job stopped at the attestation:

Error: Could not find subject at path msi/*/*.msi

download-artifact@v8 extracts a single artifact matched by pattern straight into path: the log says Starting download of artifact to: …/msi, not …/msi/msi-x64. The attach job now downloads each artifact by name, as the test job already does, and attests and uploads msi/*.msi.

The attach job is skipped on pull requests, so the checks here do not exercise it.

After merging

Run Installers by hand from main for the existing release:

gh workflow run installers.yml --ref main -f tag=v0.3.0

It builds from the v0.3.0 tag, attaches both MSIs with their attestation, and adds the Windows installers section to the notes. That edit is also what makes SourceForge copy them. This is the recovery CONTRIBUTING's Releasing describes. The attestation will name main as the workflow's ref, since that is where it runs from; gh attestation verify <file> --repo Nelsar/Axia passes either way.

download-artifact@v8 puts a single artifact matched by `pattern` straight into `path`, so the MSIs
were in msi/, not msi/msi-x64/, and the attestation found nothing at msi/*/*.msi: the run for
v0.3.0 built and tested both installers, then attached neither. The attach job now downloads each
artifact by name, as the test job does, and takes msi/*.msi.

The job runs only for a release or by hand, so no pull request exercises it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Nelsar
Nelsar merged commit 72fae4c into main Oct 23, 2026
11 checks passed
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