[Feature]: Setup Windows Release in ForgeJo #61
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
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ai-collab/bulk-image-organizer#61
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Problem or use case
Windows releases aren't automatic
Proposed solution
BulkImageOrganizer_[VER].exeBulkImageOrganizer_[DEV_BRANCH_NAME].exe(strip branch name characters to compatible file name characters)Alternatives considered
No response
Implemented on
0.1.23/issue-61-windows-release(release 0.1.24).Delivered:
.github/workflows/windows-release.yml—windows-fullhost runner builds when compiled inputs change; publisheswindows-latestonmainanddev-latest-{branch-slug}on dev branches; prunes dev releases on branch delete.scripts/manual-build-windows.ps1—-CiModewith persistent Nuitka/pip cache; packaged resource self-test.scripts/publish-windows-release.ps1— Forgejo release upsert + exe upload via curl API.scripts/prune-windows-dev-release.py— dev release cleanup.core/version.pyhelpers for branch slug, dev exe basename, and release tags.core/resource_paths.py/main.py— bundled resource resolution for Windows onefile (also fixes #32).Windows CI publish verified on the host runner. PR to
mainfollows.