Skip to content

Waymark 0.1.0

Choose a tag to compare

@github-actions github-actions released this 06 Nov 16:54
· 31 commits to master since this release
91a25e8

The first public release of Waymark: a local-first, Git-friendly work-item
tracker whose work items are Markdown documents in your repository.

Install

Prebuilt archives are attached below for Linux x86_64, macOS (Apple silicon and
Intel), and Windows x86_64, each with a .sha256 checksum. Download the archive
for your platform, verify the checksum, extract it, and put the extracted
directory on PATH. The Web package is the same two binaries with the read-only
Web view compiled in.

See the install instructions
for per-platform commands, the macOS Gatekeeper note, and the Windows
SmartScreen note.

Linux binaries

The Linux archives need glibc 2.34 or newer (Ubuntu 22.04+, Debian 12+, RHEL 9+).
On hosts with glibc older than 2.39 the dynamic loader may print a harmless
weak version 'GLIBC_2.39' not found note; the binaries still run.

Added

  • waymark, a local-first work-item tracker that stores each work item as a
    Markdown document with YAML frontmatter under the project's storage root and
    keeps project configuration in .waymark/.
  • Project initialisation and work-item reads and writes: init, create,
    show, title, body, field, owner, move, status, start,
    close, reopen, and archive.
  • Relationships and structure: parent, link, dependency, tree, and
    dep, including hierarchy and dependency trees.
  • Collection reads: list, ready, blocked, query, search, and stats,
    with shared filtering, sorting, paging, projection, and archive ranges.
  • Project operations: project, git, config, migrate, doctor,
    validate, and the generated capability reference agent-doc.
  • waymark-mcp, a Model Context Protocol server over stdio that exposes the
    same project operations to agents.
  • Two prebuilt variants from one tag: the basic package (waymark and
    waymark-mcp) and the Web package with the read-only Web view.
  • Prebuilt archives for Linux x86_64, macOS Apple silicon, macOS Intel, and
    Windows x86_64 (MSVC), named waymark-v<version>-<os>-<arch>.tar.gz and
    waymark-web-v<version>-<os>-<arch>.tar.gz, or the matching .zip on
    Windows, each with a .sha256 sidecar, a README, both licence files, and
    THIRD_PARTY_LICENSES.txt.
  • The Web view's cache and index status dashboard, opened from the header
    instead of occupying the page: projection completeness and freshness,
    lifetime cache counters, and a paged active-item index.
  • waymark serve, available in both builds: the Web package serves the
    read-only view on loopback at port 7331 by default, with --port and
    --open; the basic package reports WEB_NOT_INCLUDED without downloading
    or installing anything.
  • waymark version reports the release version and the capabilities compiled
    into the build; waymark version --json adds the embedded frontend manifest
    for a Web build.
  • Embedded frontend provenance: an assets-manifest.json records the version,
    commit, build id, and per-file SHA-256 hashes, and the release checks compare
    it with the served index.html.
  • Installation documentation with per-platform archives, checksum
    verification, first commands, the macOS Gatekeeper note, the Windows
    SmartScreen note for unsigned binaries, and the basic-to-Web upgrade path.
  • docs/mcp-clients.md with stdio configuration examples for Claude Code,
    DSH, and a generic JSON client.
  • Dual licensing under MIT or Apache-2.0.

Fixed

  • A read-only .waymark/.gitignore now stops waymark init seeding and
    waymark config set with LOCK_FAILED; previously a local user.toml could
    be written even though the ignore file that should have tracked it could not
    be updated.

Security

  • Release artifacts carry SHA-256 checksums and a cargo-about
    dependency-licence inventory.
  • The Web view is read-only, binds loopback only, and offers no LAN or public
    binding.
  • The binaries do not download or install anything at run time.
  • macOS binaries are unsigned and not notarized; Gatekeeper therefore requires
    explicit approval on first launch, as documented in the README. Windows
    binaries are unsigned too, so SmartScreen may require the same explicit
    approval.