stackpatch 2.0 release

critical CVE addressed
better archive handling
UI feedback in filemanager
Fixed console scroll

stackpatch 1.9 release

networking settings
payload size configuration

stackpatch 1.8 release

stable release

stackpatch 1.7 release

reworked muted startup flow, prod

stackpatch 1.6 release

Reworked Auth
Pushed production build
Fixed port binding issue
Branding
Console Color Issue forced with force_color 1

stackpatch 1.5 release

add optional CPU and memory limiting via Windows Job Objects + Notifications panel wide

• per-instance job objects with configurable memory and CPU rate caps
• memory-limit exits detected and surfaced as crashed with reason
• full job handle lifecycle audit; all release paths covered
• resources tab in Instance Settings; null = unlimited

stackpatch 1.4 release

changed binding port to '0.0.0.0' to allow for remote connections, should have been done upon initial commit, silly me!

stackpatch 1.3 release

Updated file manager UI UX, more versatile and handles edge-cases where file is downloadable but also editable. Google material icons are now being used to display file types in a user friendly way. -- https://fonts.google.com/icons

stackpatch 1.2 release

Daemon now starts before panel, resolves edge cases where service may be closed forcefully before initialization, causing failure on next start. Also removed un-used branding image

stackpatch 1.1 release

default cred hint added to login.tsx
default creds noted in readme.md