Windows release automation and bundled resource fix (0.1.24) #63
No reviewers
Labels
No labels
Kind/Bug
Kind/Feature
Priority/High
Priority/Medium
Reviewed/Confirmed
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ai-collab/bulk-image-organizer!63
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "0.1.23/issue-61-windows-release"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Automates Forgejo Windows release publishing (closes #61) and fixes bundled Help/resources on Windows onefile builds (closes #32).
Changes
windows-release.ymlbuilds on thewindows-fullhost runner when compiled inputs change; publisheswindows-latestfrommainanddev-latest-{branch-slug}from development branches; prunes dev releases when a branch is deleted.manual-build-windows.ps1-CiModereuses a persistent Nuitka/pip cache; verifies output with--bio-packaging-self-test.publish-windows-release.ps1upserts Forgejo releases and uploads the.exevia curl against the public API.resource_paths.pydetects Nuitka frozen runtimes withoutsys.frozen, resolves the versioned onefile unpack cache, and locates bundledUSER_GUIDE.mdand icons correctly on Windows.Testing
pytest(packaging, onefile cache, version helpers)Adds a windows-full host workflow that builds onefile executables on push, publishes windows-latest on main and dev-latest-{branch} on development branches, and deletes dev releases when branches are removed.