Repository navigation
Releases
Waymark 0.2.0
Waymark 0.2.0 is the cross-item write consent release. Updating your work items
is a statement about your own items; reaching into someone else's now needs
both consent and ownership.
Added
--cascadeonarchive,link add,link remove, andcreate, and the
same optional boolean on the MCP tools that map to them. It is the consent a
command gives for writing a second work item, and it authorizes only the
caller's own items.- Two error codes for a cross-item write:
OWNED_BY_OTHER(the other item
belongs to someone else, so re-running cannot help) and
CASCADE_CONSENT_REQUIRED(registered for callers that can supply consent;
no current command raises it). ONE_SIDED_SOFT_LINK:doctorandshowreport a soft link that one side
records and the other does not, naming the side that is missing it.CLOSED_PARENT: an active item whose direct parent is closed is labelled in
listandready, and reported as an informational finding bydoctor.
Nothing is written and no readiness changes.- Archive results list the documents it left untouched and who still references
the archived item, so retiring one item no longer hides who was affected. createandlink addresults report the documents they left untouched,
with each partner's owner and whether it is the operator's.
Changed
- Archive no longer rewrites another owner's document. It strips inbound
references only from documents the operator owns, and leaves the rest in place
with adoctorfinding for its owner to resolve.HAS_ACTIVE_CHILDRENstill
refuses an item with live children. link addwithout--cascadeno longer writes the other item. It records the
link on the caller's item and reports the partner as one-sided; re-running
from the other side completes the pair.link removewithout--cascaderemoves the link from the caller's item
only. Removing a link is a statement about one's own item; adding one is a
claim about both.create --linkwithout--cascadeno longer rewrites the referenced item.- Ownership for cross-item writes resolves the operator the same way everything
else does:.waymark/user.toml, then Gituser.name. A project with no
operator refuses a cross-item write rather than silently skipping it.
Breaking
- A command that rewrites a second document without
--cascadenow leaves that
document alone; a caller relying on the old two-sided write must pass the flag
and own the other item.
Install
Prebuilt archives are attached below for Linux, macOS (Apple silicon and
Intel), and Windows. Verify each archive against its .sha256 sidecar before
running it: the macOS and Windows binaries are unsigned.
With a Rust toolchain, the same binaries also install from crates.io:
cargo install waymark-cli # the `waymark` binary
cargo install waymark-mcp # the MCP serverThe CLI crate is waymark-cli, not waymark: waymark on crates.io is an
unrelated crate.
Full Changelog: v0.1.4...v0.2.0
Waymark 0.1.3
What's Changed
- ci: gate the published dependency versions on the workspace version by @QiYueran-source in #23
- docs(mcp): add a crate README and searchable crates.io metadata by @QiYueran-source in #24
- chore(mcp): add the registry manifest for waymark-mcp 0.1.3 by @QiYueran-source in #25
- release: 0.1.3 by @QiYueran-source in #26
Full Changelog: v0.1.2...v0.1.3
Waymark 0.1.2
This patch release publishes the workspace to crates.io and refreshes the README artwork.
Added
waymark-core,waymark-web,waymark-mcp, andwaymark-cliare published to crates.io, socargo install waymark-cliinstalls thewaymarkbinary andcargo install waymark-mcpinstalls the MCP server. The CLI crate is namedwaymark-clibecausewaymarkon crates.io is an unrelated crate.
Changed
- The release workflow publishes those four crates in dependency order after a reviewer approves the
crates-iodeployment; a pre-release tag still produces a GitHub pre-release and no crates.io version. - The README banner and the GitHub social preview use the new Waymark artwork; the 1280x400 README crop and the 1280x640 social card are both refreshed.
Install
Download the archive for your platform from the assets below and verify its .sha256 sidecar before extracting:
- Basic package:
waymark-v0.1.2-linux-x86_64.tar.gz,waymark-v0.1.2-macos-aarch64.tar.gz,waymark-v0.1.2-macos-x86_64.tar.gz, orwaymark-v0.1.2-windows-x86_64.zip. - Web package: the matching
waymark-web-v0.1.2-*archive, which addswaymark serveand the embedded Web view.
With a Rust toolchain the same binaries install from crates.io, without an archive:
cargo install waymark-cli # the `waymark` binary
cargo install waymark-mcp # the MCP serverThe basic package reports WEB_NOT_INCLUDED for waymark serve; install the Web package for the browser view.
Full changelog: https://github.com/QiYueran-source/waymark/blob/v0.1.2/CHANGELOG.md
Waymark 0.1.1
This patch release updates the read-only Web view's header and ships the documentation work that landed after 0.1.0.
Changed
- The Web view now shows the Waymark logo in the header, replacing the three-bar placeholder mark. The frontend is embedded in the Web package, so install the new
waymark-web-v0.1.1-*archive to pick up the logo; replacing files under the v0.1.0 release is not supported. - The README opens with the pitch, a first-run transcript, the capabilities the tracker guarantees, and who should not use it, followed by the package and installation reference.
README.zh-CN.mdcarries the same structure. - The README landing section now includes a replaceable banner asset; the same 1280x640 source also exports a 1280x400 README crop and a GitHub social preview.
Added
SECURITY.md, covering the supported versions, the private reporting channel, the response targets, and the security scope of the CLI, the MCP server, and the Web view.README.zh-CN.md, a Simplified Chinese translation of the README, linked from the English one.- Every release archive now ships
README.zh-CN.mdandSECURITY.md, so the links in the packagedREADME.mdresolve.
Fixed
- The first-run transcript in the README matches the output of
waymark init,waymark create, andwaymark list.
Install
Download the archive for your platform from the assets below and verify its .sha256 sidecar before extracting:
- Basic package:
waymark-v0.1.1-linux-x86_64.tar.gz,waymark-v0.1.1-macos-aarch64.tar.gz,waymark-v0.1.1-macos-x86_64.tar.gz, orwaymark-v0.1.1-windows-x86_64.zip. - Web package: the matching
waymark-web-v0.1.1-*archive, which addswaymark serveand the embedded Web view.
The basic package reports WEB_NOT_INCLUDED for waymark serve; install the Web package for the browser view.
Waymark 0.1.0
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, andarchive. - Relationships and structure:
parent,link,dependency,tree, and
dep, including hierarchy and dependency trees. - Collection reads:
list,ready,blocked,query,search, andstats,
with shared filtering, sorting, paging, projection, and archive ranges. - Project operations:
project,git,config,migrate,doctor,
validate, and the generated capability referenceagent-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 (
waymarkand
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), namedwaymark-v<version>-<os>-<arch>.tar.gzand
waymark-web-v<version>-<os>-<arch>.tar.gz, or the matching.zipon
Windows, each with a.sha256sidecar, 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--portand
--open; the basic package reportsWEB_NOT_INCLUDEDwithout downloading
or installing anything.waymark versionreports the release version and the capabilities compiled
into the build;waymark version --jsonadds the embedded frontend manifest
for a Web build.- Embedded frontend provenance: an
assets-manifest.jsonrecords the version,
commit, build id, and per-file SHA-256 hashes, and the release checks compare
it with the servedindex.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.mdwith 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/.gitignorenow stopswaymark initseeding and
waymark config setwithLOCK_FAILED; previously a localuser.tomlcould
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.