Skip to content

CI: attach release zip (DLL + readme.txt) to match past releases - #19

Merged
k3it merged 1 commit into
masterfrom
claude/release-publishing-workflow-lo1yr3
Aug 9, 2026
Merged

k3it merged 1 commit into
masterfrom
claude/release-publishing-workflow-lo1yr3

Conversation

@k3it

@k3it k3it commented Aug 9, 2026

Copy link
Copy Markdown
Owner

Follow-up to #18. Restores the historical release-asset format: instead of attaching a bare HermesIntf.dll, the release workflow now packages the DLL together with readme.txt into HermesIntf-<version>.zip and attaches that.

Change (.github/workflows/msbuild.yml)

  • On a published release, Compress-Archive bundles HermesIntf.dll + readme.txt into HermesIntf-<version>.zip (version derived from the release tag with the leading v stripped), then attaches it via gh release upload.
  • Naming matches prior releases, e.g. HermesIntf-24.1.13.zip → the next one will be HermesIntf-26.8.9.zip.

This affects future releases; the current v26.8.9 release already has its DLL attached. If you want the zip on v26.8.9 too, re-publishing that release (or re-running its workflow) after this merges will produce and attach it.

🤖 Generated with Claude Code

https://claude.ai/code/session_01SsVwSNXUxxufvxfb63DbT4


Generated by Claude Code

On a published release, package HermesIntf.dll and readme.txt into
HermesIntf-<version>.zip (matching the historical release asset naming,
e.g. HermesIntf-24.1.13.zip) and attach that to the release.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SsVwSNXUxxufvxfb63DbT4
@k3it
k3it merged commit d869fb1 into master Aug 9, 2026
1 check 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