Release: ship okf-windows-x64.exe alongside the linux and macOS binaries

Open Beginner friendly
#43 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
88/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
dart
Domain
ci-cd, release

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 --version prints okf <version> on windows-latest.
  • gh release verify-asset succeeds 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
1d 1h
Merged PRs (30d)
31

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from conceptadev/okf

All issues in conceptadev/okf

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.