* refactor(repo): move OpenWork apps into apps and ee layout
Rebase the monorepo layout migration onto the latest dev changes so the moved app, desktop, share, and cloud surfaces keep working from their new paths. Carry the latest deeplink, token persistence, build, Vercel, and docs updates forward to avoid stale references and broken deploy tooling.
* chore(repo): drop generated desktop artifacts
Ignore the moved Tauri target and sidecar paths so local cargo checks do not pollute the branch. Remove the accidentally committed outputs from the repo while keeping the layout migration intact.
* fix(release): drop built server cli artifact
Stop tracking the locally built apps/server/cli binary so generated server outputs do not leak into commits. Also update the release workflow to check the published scoped package name for @openwork/server before deciding whether npm publish is needed.
* fix(workspace): add stable CLI bin wrappers
Point the server and router package bins at committed wrapper scripts so workspace installs can create shims before dist outputs exist. Keep the wrappers compatible with built binaries and source checkouts to avoid Vercel install warnings without changing runtime behavior.
Use the configured larger-runner label for both Linux release matrix targets so x86_64 and aarch64 builds share the same faster GitHub-hosted runner path and logging.
Allow release and desktop workflows to target the new GitHub-hosted larger runner without hard-coding it, while keeping ubuntu-22.04 as a fallback and logging the effective runner selection.
* Initial plan
* Add ARM64 build support to workflows and AUR packaging
Co-authored-by: koubas <1354930+koubas@users.noreply.github.com>
* Fix: Add noextract field update to AUR script
Co-authored-by: koubas <1354930+koubas@users.noreply.github.com>
* Add comment explaining temporary SKIP checksum for ARM64
Co-authored-by: koubas <1354930+koubas@users.noreply.github.com>
* Make cross-compilation tools conditional on runner architecture
Cross-compilation tools (gcc-aarch64-linux-gnu) are now only installed when actually cross-compiling (x86_64 → ARM64). Native ARM64 runners will use native compilation without these tools.
This enables flexible deployment:
- Default: Cross-compilation on ubuntu-22.04 (free tier)
- Optional: Native compilation on ubuntu-*-arm64 or self-hosted ARM64 runners
The workflow auto-detects via runner.arch context.
Co-authored-by: koubas <1354930+koubas@users.noreply.github.com>
* Remove cross-compilation tools installation for native ARM64 runners
Since we're running on native ARM64 runners, cross-compilation tools are not needed. The native toolchain will be used directly for ARM64 builds.
This simplifies the workflow and improves build performance by removing unnecessary package installation.
Co-authored-by: koubas <1354930+koubas@users.noreply.github.com>
* Refactor: Extract SHA256 checksum calculation to reusable function
Eliminates code duplication by creating a single compute_sha256() function
that is called twice, instead of duplicating the Python code block.
Benefits:
- Reduced script from 132 to 123 lines (9 lines saved)
- Single source of truth for checksum logic
- Easier to maintain and modify in the future
- Follows DRY (Don't Repeat Yourself) principle
Co-authored-by: koubas <1354930+koubas@users.noreply.github.com>
* Fix: Update comment to use consistent terminology
Co-authored-by: koubas <1354930+koubas@users.noreply.github.com>
* Replace Python SHA256 hashing with native sha256sum command
Simplifies the compute_sha256() function by replacing the Python implementation
with native bash sha256sum command, reducing complexity and improving performance.
Changes:
- Replaced 13-line Python function with 1-line sha256sum call
- Reduced script from 123 to 113 lines (10 lines saved)
- Eliminated Python interpreter startup overhead for hashing
- Maintains full compatibility with existing checksums
Benefits:
- Simpler, more idiomatic bash implementation
- Faster execution (no Python startup for hashing)
- Easier to read and maintain
Co-authored-by: koubas <1354930+koubas@users.noreply.github.com>
* Remove compute_sha256 function and inline sha256sum usage
Eliminates the compute_sha256() wrapper function and directly inlines
sha256sum calls, making the code simpler and more transparent.
Changes:
- Removed function definition (lines 46-49)
- Inlined sha256sum calls directly where needed
- Reduced script from 113 to 108 lines (5 lines saved)
- Updated comment to reflect direct usage
Benefits:
- Simpler code with fewer abstractions
- More direct and transparent implementation
- Easier to understand at a glance
Co-authored-by: koubas <1354930+koubas@users.noreply.github.com>
* Remove useless comments from update-aur.sh
* foo
* bar
* Bring back ARM64 cross-compilation tools
* Add Linux-ARM64-build-and-release branch to workflow
* wip
---------
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: koubas <1354930+koubas@users.noreply.github.com>
Co-authored-by: Benjamin Shafii <benjamin.shafii@gmail.com>
- Allow OpenWork workflows to pull the OpenCode CLI sidecar from a configurable GitHub repo + version (OPENCODE_GITHUB_REPO/OPENCODE_VERSION).\n- Make Settings > Debug show OpenCode binary source + version (e.g. bundled · 1.1.60-openwork.1).
Stop pinning OpenCode in package metadata and resolve the latest release during sidecar bundling/runtime, while still allowing OPENCODE_VERSION to pin for reproducible builds.
- Add ensure_owpenbot_sidecar() to build.rs to create debug stubs when binary missing
- Remove 'if: matrix.os_type == windows' from Bun setup in CI workflows
- This fixes PreRelease builds failing because prepare:sidecar needs bun to compile owpenbot
