Release: ship okf-windows-x64.exe alongside the linux and macOS binaries
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
Research direction
Start with tool/ci/platforms.tsv and compare the existing Linux and macOS rows with the release tooling that consumes this table. Validate a tagged release on windows-latest, confirm that okf-windows-x64.exe is attached and executable, and run ./okf-windows-x64.exe --version plus gh release verify-asset.
Written by the indexing model from the issue text.
Description
What and why
conceptadev/okf-profile is making the Profile tooling usable without a Dart SDK (okf-profile#53): a Claude Code plugin registers okf mcp knowledge, and one-line installers put okf and okfp on PATH on macOS, Linux, and Windows. okfp gains okfp-windows-x64.exe in that work; the Windows installer then needs the matching okf binary from this repository's releases.
Ask
Add a Windows row to tool/ci/platforms.tsv so releases attach okf-windows-x64.exe:
Windows X64 windows-latest okf-windows-x64.exe
On the okf-profile side the grinder needed no change: cli_pkg's pkg-compile-native writes build/<name>.native on every platform, the build task copies it to $ASSET, and the chmod is already guarded on Windows. verify-engine-version.sh is invoked through bash explicitly, so it runs under the runner's git-bash. The same should hold here since the release tooling is the same shape.
Acceptance
- A release tag attaches
okf-windows-x64.exe;./okf-windows-x64.exe --versionprintsokf <version>onwindows-latest. -
gh release verify-assetsucceeds for it (immutable releases are already on here).
Blocks the Windows acceptance criterion of okf-profile#53.
- Dominant language
- Dart
- Stars
- 0
- Forks
- 0
- Avg merge
- 4h 39m
- Merged PRs (30d)
- 4
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from btwld/okf
-
Difficulty 3/5 1-2 days Newbie friendliness 78/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
afk enhancement
Difficulty 4/5 3-5 days Newbie friendliness 68/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
AppFlowy-IO/AppFlowy#9147 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
ccch1mneyyy/dsh-Go#1682 ·
Maintainers usually reply within 1 day
-
help wanted
Difficulty 1/5 Under an hour Newbie friendliness 76/100
pesaclarity/ujumbe-parsers#64 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
patarapolw/lingua_srs#278 ·
Maintainers usually reply within 1 day