release: prep v1.3.1-rc.1 (#6593)
* release: prep v1.3.1-rc.1 Sanctioned RC bump per RELEASING.md "Cut an RC", on the #6298 model: ./scripts/update-versions.sh 1.3.1-rc.1, which carries the stamp into version.go, the three plugin.json manifests, marketplace.json, the npm package.json, the MCP pyproject.toml/__init__.py/uv.lock, default.nix, the ten .githooks managed-section markers and the winres strings. scripts/check-versions.sh passes all 24 gates at 1.3.1-rc.1. Unlike the 1.3.0 RCs, this bump moves the BASE version, so cmd/bd/winres/manifest.xml changes too (1.3.0.0 -> 1.3.1.0) along with the winres numeric file_version/product_version (1.3.0 -> 1.3.1). Those PE fields must be purely numeric; the FileVersion/ProductVersion strings carry the full 1.3.1-rc.1, and uv.lock carries the PEP 440 normalization 1.3.1rc1 written by `uv lock`, never by hand. This has to land before the tag: release.yml's verify-version-consistency compares ${GITHUB_REF_NAME#v} byte-for-byte against the Version string in cmd/bd/version.go, and every stamp on this branch still read 1.3.0. Simulated against the working tree with the workflow's own grep/sed pipeline: the extracted string is exactly "1.3.1-rc.1", on a single matching line. The tag must be spelled v1.3.1-rc.1. CHANGELOG: creates the [1.3.1] section dated 2026-09-16 and leaves [Unreleased] empty but present, which is what #6038 (b3ef65c85) did when it created [1.3.0] at branch-cut, and what #6298's fixup established for an RC tag — an entry parked under [Unreleased] ships in no release by Keep-a-Changelog semantics, yet the RC demonstrably ships it. The three Fixed bullets already on the branch (#6580 x2, #6578) move under [1.3.1] by the rename alone; their wording is untouched, and the shipped [1.3.0] section and everything below it is byte-identical (sha256 of the [1.3.0]-to-EOF region is unchanged across this commit). The 2026-09-16 date is provisional. The final 1.3.1 prep must hand-restamp it to the real release date rather than rerun the beads-release formula's stamp-changelog step, which sed-inserts a fresh header under [Unreleased] and never re-dates an existing section — running it against an already dated [1.3.1] duplicates the heading. Same trap #6298 documented and #6564 then worked around. cmd/bd/info.go: adds the 1.3.1-rc.1 digest at index 0 of versionChanges, dated 2026-09-16 so the array stays newest-first with monotonic dates for TestGetVersionsSinceOrder. It leads with the no-migration note (a 1.3.0 user's upgrade is a binary swap) and then digests the two #6580 changes and the two #6578 ones. Per the #6298 lesson this key can only reach rc.1 users by shipping inside the rc.1 binary; omit it and `bd upgrade review` dumps the whole history at them. docs/cli-docs.pin is still v1.2.2 on this branch — 1.3.0's docs-pin step never happened. check-versions.sh explicitly excludes it, so it is not tag-blocking and is deliberately left for the post-tag docs step. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * docs(release): reclassify 1.3.1 behaviour changes and document the config migration Documentation-only amendment to the v1.3.1-rc.1 prep. No version stamp is touched; ./scripts/check-versions.sh stays 24/24 at 1.3.1-rc.1. Three corrections, all inside the `## [1.3.1]` section and its `cmd/bd/info.go` `versionChanges` twin. 1. The flat->nested config migration is now documented (#6594). #6578 made `bd config set <dotted.key>` write a nested mapping, and where a flat top-level key of the same literal name exists it deletes that entry and re-emits the value nested (`updateNestedYamlKey`). `.beads/config.yaml` is not exclusively bd's, so another writer that reads its dotted keys flat stops seeing any value migrated this way — and if it re-adds the flat key, bd's own readers disagree: Viper-backed reads return the flat value while GetStringFromDir returns the nested one. Verified both halves empirically against this tree (dual-spelling probe: viper="flatvalue", GetStringFromDir="nestedvalue", independent of document order; migration probe: `dolt.host` flat entry deleted, sibling `dolt.port` and `other.thing` byte-intact). Realistic collisions are `dolt.*`, `export.auto`, `backup.enabled`. 2. Two genuine behaviour changes moved out of `### Fixed` into `### Changed`, following the 1.3.0-rc.2 precedent inc1e5e49e3: the `bd dolt status --json` shape change (#6580), which a parser of the old payload meets on upgrade, and the two `bd config set` success->failure cases (#6578). The fix content stays in `Fixed` with a pointer; neither statement appears in both sections. 3. `backend_endpoint` added to the documented key list in both CHANGELOG.md and info.go. It is a real `omitempty` field on `proxiedDoltStatus` (cmd/bd/dolt_proxied_lifecycle.go:63), set only when the sidecar reports an external backend — the one topology where `backend_managed` is false and nothing else names the server. Both surfaces now carry the same 11 keys as the struct. Validated: `## [1.3.0]`->EOF is byte-identical before and after (sha256 798a2ee0b0f0b7a3f0fc017ae01c919807740348a34f5ea8719b82a008533d00); exactly one `## [1.3.1]` heading, `## [Unreleased]` present and empty; check-versions.sh 24/24; go build/vet ./...; go test ./cmd/bd -run 'TestGetVersionsSinceOrder|TestVersionChangesStructure|TestVersionChangesCoverage|TestVersionChangesJSON|TestGetVersionsSince|TestDisplayVersion' all PASS, no skips; scripts/ci/pr-lint.sh and scripts/ci/pr-policy.sh green; `bd info --whats-new` surfaces both amendments end-to-end. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
parent
fa95439006
commit
d487b9796e
19 changed files with 93 additions and 42 deletions
|
|
@ -9,7 +9,7 @@
|
|||
"name": "beads",
|
||||
"source": "./plugins/beads",
|
||||
"description": "AI-supervised issue tracker for coding workflows",
|
||||
"version": "1.3.0"
|
||||
"version": "1.3.1-rc.1"
|
||||
}
|
||||
]
|
||||
}
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
#!/usr/bin/env sh
|
||||
# --- BEGIN BEADS INTEGRATION v1.3.0 ---
|
||||
# --- BEGIN BEADS INTEGRATION v1.3.1-rc.1 ---
|
||||
# This section is managed by beads. Do not remove these markers.
|
||||
if command -v bd >/dev/null 2>&1; then
|
||||
export BD_GIT_HOOK=1
|
||||
|
|
@ -56,4 +56,4 @@ if command -v bd >/dev/null 2>&1; then
|
|||
fi
|
||||
if [ "$_bd_exit" -ne 0 ]; then exit "$_bd_exit"; fi
|
||||
fi
|
||||
# --- END BEADS INTEGRATION v1.3.0 ---
|
||||
# --- END BEADS INTEGRATION v1.3.1-rc.1 ---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
#!/usr/bin/env sh
|
||||
# --- BEGIN BEADS INTEGRATION v1.3.0 ---
|
||||
# --- BEGIN BEADS INTEGRATION v1.3.1-rc.1 ---
|
||||
# This section is managed by beads. Do not remove these markers.
|
||||
if command -v bd >/dev/null 2>&1; then
|
||||
export BD_GIT_HOOK=1
|
||||
|
|
@ -56,4 +56,4 @@ if command -v bd >/dev/null 2>&1; then
|
|||
fi
|
||||
if [ "$_bd_exit" -ne 0 ]; then exit "$_bd_exit"; fi
|
||||
fi
|
||||
# --- END BEADS INTEGRATION v1.3.0 ---
|
||||
# --- END BEADS INTEGRATION v1.3.1-rc.1 ---
|
||||
|
|
|
|||
|
|
@ -40,7 +40,7 @@ if [ -n "$staged_go_files" ]; then
|
|||
echo "$staged_go_files" | xargs git add
|
||||
fi
|
||||
|
||||
# --- BEGIN BEADS INTEGRATION v1.3.0 ---
|
||||
# --- BEGIN BEADS INTEGRATION v1.3.1-rc.1 ---
|
||||
# This section is managed by beads. Do not remove these markers.
|
||||
if command -v bd >/dev/null 2>&1; then
|
||||
export BD_GIT_HOOK=1
|
||||
|
|
@ -97,4 +97,4 @@ if command -v bd >/dev/null 2>&1; then
|
|||
fi
|
||||
if [ "$_bd_exit" -ne 0 ]; then exit "$_bd_exit"; fi
|
||||
fi
|
||||
# --- END BEADS INTEGRATION v1.3.0 ---
|
||||
# --- END BEADS INTEGRATION v1.3.1-rc.1 ---
|
||||
|
|
|
|||
|
|
@ -39,7 +39,7 @@ fi
|
|||
|
||||
exec < <(printf '%s\n' "$push_refs")
|
||||
|
||||
# --- BEGIN BEADS INTEGRATION v1.3.0 ---
|
||||
# --- BEGIN BEADS INTEGRATION v1.3.1-rc.1 ---
|
||||
# This section is managed by beads. Do not remove these markers.
|
||||
if command -v bd >/dev/null 2>&1; then
|
||||
export BD_GIT_HOOK=1
|
||||
|
|
@ -96,4 +96,4 @@ if command -v bd >/dev/null 2>&1; then
|
|||
fi
|
||||
if [ "$_bd_exit" -ne 0 ]; then exit "$_bd_exit"; fi
|
||||
fi
|
||||
# --- END BEADS INTEGRATION v1.3.0 ---
|
||||
# --- END BEADS INTEGRATION v1.3.1-rc.1 ---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
#!/usr/bin/env sh
|
||||
# --- BEGIN BEADS INTEGRATION v1.3.0 ---
|
||||
# --- BEGIN BEADS INTEGRATION v1.3.1-rc.1 ---
|
||||
# This section is managed by beads. Do not remove these markers.
|
||||
if command -v bd >/dev/null 2>&1; then
|
||||
export BD_GIT_HOOK=1
|
||||
|
|
@ -56,4 +56,4 @@ if command -v bd >/dev/null 2>&1; then
|
|||
fi
|
||||
if [ "$_bd_exit" -ne 0 ]; then exit "$_bd_exit"; fi
|
||||
fi
|
||||
# --- END BEADS INTEGRATION v1.3.0 ---
|
||||
# --- END BEADS INTEGRATION v1.3.1-rc.1 ---
|
||||
|
|
|
|||
73
CHANGELOG.md
73
CHANGELOG.md
|
|
@ -7,6 +7,56 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|||
|
||||
## [Unreleased]
|
||||
|
||||
## [1.3.1] - 2026-09-16
|
||||
|
||||
### Changed
|
||||
|
||||
- **`bd dolt status --json` changes shape on a proxied workspace**
|
||||
([#6580](https://github.com/gastownhall/beads/pull/6580)). It now emits
|
||||
`{"mode": "proxied-server", "root": ..., "running": <proxy up>, "proxy_pid":
|
||||
..., "proxy_port": ..., "backend_managed": ..., "backend_running": ...,
|
||||
"backend_pid": ..., "backend_port": ..., "backend_endpoint": ...,
|
||||
"idle_timeout": ...}` instead of the always-false `{"running": false, "pid":
|
||||
0, "port": 0}` — `pid` and `port` are gone, replaced by the `proxy_*` and
|
||||
`backend_*` pairs. `running` no longer reports a bd-managed dolt PID file; it
|
||||
describes the proxy, the endpoint every bd command connects through, so it is
|
||||
now usually true where it used to be always false. `backend_managed` is false
|
||||
on external proxied topologies, where the dolt server is not bd's process to
|
||||
report on and `backend_endpoint` names it instead. Anything parsing the old
|
||||
payload changes behaviour on upgrade. Direct-server, shared, embedded and
|
||||
externally-managed workspaces keep the output they had.
|
||||
|
||||
- **`bd config set <dotted.key>` deletes a flat top-level key of the same
|
||||
literal name** ([#6578](https://github.com/gastownhall/beads/pull/6578)).
|
||||
Dotted keys are now written as a nested mapping (see **Fixed** below for why),
|
||||
and where the file already carried the flat spelling — a top-level key whose
|
||||
*name* contains the dot, such as `dolt.host: "10.0.0.1"` — that entry is
|
||||
removed and the value re-emitted under `dolt:`. Only the key being written is
|
||||
touched; other dotted keys, including ones bd did not write, are left exactly
|
||||
as they are.
|
||||
|
||||
`.beads/config.yaml` is not exclusively bd's, so this can be visible outside
|
||||
bd: an external tool that both writes *and* reads flat dotted keys there will
|
||||
stop seeing any value bd migrates this way. Any dotted key bd stores in
|
||||
`config.yaml` rather than the database can collide; in practice that means
|
||||
`dolt.*`, `export.auto`, and `backup.enabled`. If the other writer then
|
||||
re-adds its flat key, the file carries both spellings and bd's own readers
|
||||
disagree — Viper-backed reads (`bd config get`, and the `dolt.auto-start`
|
||||
lookup on the store-open path) return the **flat** value, while
|
||||
`GetStringFromDir` returns the **nested** one, so a `bd config set` can be
|
||||
shadowed by a stale flat entry. Tracked as
|
||||
[#6594](https://github.com/gastownhall/beads/issues/6594). Until that lands,
|
||||
in a workspace whose config another tool maintains, let that tool own its
|
||||
keys, or check `.beads/config.yaml` for a duplicated key after running
|
||||
`bd config set`.
|
||||
|
||||
- **Two `bd config set` writes that used to exit 0 now exit 1**
|
||||
([#6578](https://github.com/gastownhall/beads/pull/6578)), because both wrote
|
||||
a value no reader could see: setting a dotted key under a parent that already
|
||||
holds a scalar (`sync: enabled`, then `bd config set sync.remote`), and
|
||||
setting one in a file whose top level is not a mapping. A script that
|
||||
tolerated the old exit 0 now has to handle the failure.
|
||||
|
||||
### Fixed
|
||||
|
||||
- **`bd dolt start` no longer puts a second sql-server over a proxied
|
||||
|
|
@ -26,15 +76,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|||
server: not running` while the proxy was serving CRUD — the wrong answer
|
||||
that sent operators to `bd dolt start` in the first place. It now reads the
|
||||
proxy's own records and reports the proxy and its dolt backend separately,
|
||||
without starting either. **JSON output shape change**: on a proxied
|
||||
workspace `bd dolt status --json` now emits
|
||||
`{"mode": "proxied-server", "root": ..., "running": <proxy up>, "proxy_pid":
|
||||
..., "proxy_port": ..., "backend_managed": ..., "backend_running": ...,
|
||||
"backend_pid": ..., "backend_port": ..., "idle_timeout": ...}` instead of
|
||||
the always-false `{"running": false, "pid": 0, "port": 0}`. `running`
|
||||
describes the proxy, the endpoint every bd command connects through;
|
||||
`backend_managed` is false on external proxied topologies, where the dolt
|
||||
server is not bd's process to report on.
|
||||
without starting either. The `--json` payload changes shape to carry that —
|
||||
see **Changed** above before parsing it.
|
||||
|
||||
- **A dotted config key now round-trips: what `bd config set` writes,
|
||||
`bd config get` and bd's own readers find**
|
||||
|
|
@ -46,16 +89,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|||
walks nested mappings, so it does not. The value was set and invisible at the
|
||||
same time depending on which reader asked, and `bd init --remote` in a fresh
|
||||
workspace was the ordinary way in: the remote was recorded and then not found.
|
||||
Dotted keys are written nested now, an existing flat spelling of the key being
|
||||
written is migrated to the nested one, and `bd config unset` removes the
|
||||
nested form — it only ever matched the flat spelling, so unsetting
|
||||
Dotted keys are written nested now, and `bd config unset` removes the nested
|
||||
form — it only ever matched the flat spelling, so unsetting
|
||||
`sync.remote` silently left the remote live. Keys the write does not own,
|
||||
including dotted ones somebody else put there, are left exactly as they are.
|
||||
|
||||
Two things that used to succeed now report an error instead, because both
|
||||
produced a value no reader could see: setting a key under a parent that
|
||||
already holds a value (`sync: enabled`, then `bd config set sync.remote`), and
|
||||
setting one in a file whose top level is not a mapping.
|
||||
Two consequences of the nested write — the flat-key migration and two new
|
||||
failure exits — are under **Changed** above.
|
||||
|
||||
## [1.3.0] - 2026-09-15
|
||||
|
||||
|
|
|
|||
|
|
@ -220,6 +220,18 @@ type VersionChange struct {
|
|||
|
||||
// versionChanges contains agent-actionable changes for recent versions
|
||||
var versionChanges = []VersionChange{
|
||||
{
|
||||
Version: "1.3.1-rc.1",
|
||||
Date: "2026-09-16",
|
||||
Changes: []string{
|
||||
"RC: first candidate for the 1.3.1 patch line, on top of 1.3.0. It carries fixes only — no schema migration, so upgrading from 1.3.0 is a binary swap. If you are coming from 1.2.2 or earlier, the [1.3.0] entry below still describes everything you meet, including the migration and backup notes; read it first.",
|
||||
"CHANGE: 'bd dolt start' on a PROXIED workspace is now a typed refusal with code 'proxy.dolt_start.conflict' instead of starting a second sql-server over the proxy's own data directory. It previously either stranded ordinary bd commands on 'invalid connection' or adopted the proxy's dolt child into bd's classic PID/port records, leaving two managers for one process. The proxy owns its backend's lifecycle: it starts on demand, and 'bd dolt stop' shuts it down. Direct-server and embedded workspaces are unaffected.",
|
||||
"CHANGE: 'bd dolt status --json' changes shape on a proxied workspace. It now reports the proxy and its dolt backend separately — {\"mode\": \"proxied-server\", \"running\": <proxy up>, \"proxy_pid\", \"proxy_port\", \"backend_managed\", \"backend_running\", \"backend_pid\", \"backend_port\", \"backend_endpoint\", \"idle_timeout\", \"root\"} — instead of the always-false {\"running\": false, \"pid\": 0, \"port\": 0} it emitted by reading a PID file proxied mode never writes. 'pid' and 'port' are gone, replaced by the proxy_*/backend_* pairs. 'running' now describes the proxy, the endpoint every bd command connects through, so it is usually true where it used to be always false; 'backend_managed' is false on external proxied topologies, where 'backend_endpoint' names the server bd does not manage. A script parsing the old payload changes behavior on upgrade.",
|
||||
"FIX: a dotted config key now round-trips — what 'bd config set' writes is what 'bd config get' and bd's own readers find. Setting a key like 'sync.remote' or 'dolt.host' into a config.yaml with no matching section used to append a top-level key whose NAME contained the dot, which Viper finds and the direct reader GetStringFromDir does not; 'bd init --remote' in a fresh workspace was the ordinary way in, recording a remote no reader could locate. Dotted keys are written nested now, an existing flat spelling is migrated, and 'bd config unset' removes the nested form (it only ever matched the flat one, so unsetting 'sync.remote' silently left the remote live).",
|
||||
"CHANGE: writing a dotted key nested has a consequence outside bd — 'bd config set <dotted.key>' DELETES a flat top-level key of the same literal name. Writing 'dolt.host' into a file that already carries a top-level 'dolt.host: \"10.0.0.1\"' removes that entry and re-emits the value under 'dolt:'; only the key being written is touched. .beads/config.yaml is not exclusively bd's, so an external tool that both writes AND reads flat dotted keys there stops seeing any value bd migrates this way. Realistic collisions are 'dolt.*', 'export.auto', and 'backup.enabled'. If that tool re-adds its flat key the file carries both spellings and bd's own readers disagree: Viper-backed reads ('bd config get', and the dolt.auto-start lookup on store open) return the FLAT value while GetStringFromDir returns the NESTED one, so a 'bd config set' can be shadowed by a stale flat entry. Tracked as #6594; until it lands, let the other tool own its keys, or check .beads/config.yaml for a duplicated key after running 'bd config set'.",
|
||||
"CHANGE: two config writes that used to exit 0 now exit 1, because both produced a value no reader could see — setting a dotted key under a parent that already holds a scalar ('sync: enabled', then 'bd config set sync.remote'), and setting one in a file whose top level is not a mapping.",
|
||||
},
|
||||
},
|
||||
{
|
||||
Version: "1.3.0",
|
||||
Date: "2026-09-15",
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ import (
|
|||
|
||||
var (
|
||||
// Version is the current version of bd (overridden by ldflags at build time)
|
||||
Version = "1.3.0"
|
||||
Version = "1.3.1-rc.1"
|
||||
// Build can be set via ldflags at compile time
|
||||
Build = "dev"
|
||||
// Commit and branch the git revision the binary was built from (optional ldflag)
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@
|
|||
<assemblyIdentity
|
||||
type="win32"
|
||||
name="beads.bd"
|
||||
version="1.3.0.0"
|
||||
version="1.3.1.0"
|
||||
processorArchitecture="*"/>
|
||||
<description>beads - AI-supervised issue tracker</description>
|
||||
<compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1">
|
||||
|
|
|
|||
|
|
@ -9,8 +9,8 @@
|
|||
"#1": {
|
||||
"0000": {
|
||||
"fixed": {
|
||||
"file_version": "1.3.0",
|
||||
"product_version": "1.3.0",
|
||||
"file_version": "1.3.1",
|
||||
"product_version": "1.3.1",
|
||||
"type": "App"
|
||||
},
|
||||
"info": {
|
||||
|
|
@ -18,12 +18,12 @@
|
|||
"Comments": "AI-supervised issue tracker for coding workflows",
|
||||
"CompanyName": "Steve Yegge",
|
||||
"FileDescription": "beads - AI-supervised issue tracker",
|
||||
"FileVersion": "1.3.0",
|
||||
"FileVersion": "1.3.1-rc.1",
|
||||
"InternalName": "bd",
|
||||
"LegalCopyright": "Copyright (c) 2024-2026 Steve Yegge. MIT License.",
|
||||
"OriginalFilename": "bd.exe",
|
||||
"ProductName": "beads",
|
||||
"ProductVersion": "1.3.0"
|
||||
"ProductVersion": "1.3.1-rc.1"
|
||||
}
|
||||
}
|
||||
}
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@
|
|||
}:
|
||||
buildGoModule {
|
||||
pname = "beads";
|
||||
version = "1.3.0";
|
||||
version = "1.3.1-rc.1";
|
||||
|
||||
src = self;
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
[project]
|
||||
name = "beads-mcp"
|
||||
version = "1.3.0"
|
||||
version = "1.3.1-rc.1"
|
||||
description = "MCP server for beads issue tracker."
|
||||
readme = "README.md"
|
||||
requires-python = ">=3.10"
|
||||
|
|
|
|||
|
|
@ -4,4 +4,4 @@ This package provides an MCP (Model Context Protocol) server that exposes
|
|||
beads (bd) issue tracker functionality to MCP Clients.
|
||||
"""
|
||||
|
||||
__version__ = "1.3.0"
|
||||
__version__ = "1.3.1-rc.1"
|
||||
|
|
|
|||
2
integrations/beads-mcp/uv.lock
generated
2
integrations/beads-mcp/uv.lock
generated
|
|
@ -175,7 +175,7 @@ wheels = [
|
|||
|
||||
[[package]]
|
||||
name = "beads-mcp"
|
||||
version = "1.3.0"
|
||||
version = "1.3.1rc1"
|
||||
source = { editable = "." }
|
||||
dependencies = [
|
||||
{ name = "fastmcp" },
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@beads/bd",
|
||||
"version": "1.3.0",
|
||||
"version": "1.3.1-rc.1",
|
||||
"description": "Beads issue tracker - lightweight memory system for coding agents with native binary support",
|
||||
"main": "bin/bd.js",
|
||||
"bin": {
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
{
|
||||
"name": "beads",
|
||||
"description": "AI-supervised issue tracker for coding workflows. Manage tasks, discover work, and maintain context with simple CLI commands.",
|
||||
"version": "1.3.0",
|
||||
"version": "1.3.1-rc.1",
|
||||
"author": {
|
||||
"name": "Steve Yegge",
|
||||
"url": "https://github.com/steveyegge"
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "beads",
|
||||
"version": "1.3.0",
|
||||
"version": "1.3.1-rc.1",
|
||||
"description": "AI-supervised issue tracking for coding workflows with agent skills.",
|
||||
"author": {
|
||||
"name": "Steve Yegge",
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
{
|
||||
"name": "beads",
|
||||
"description": "AI-supervised issue tracker for coding workflows. Manage tasks, discover work, and maintain context with simple CLI commands.",
|
||||
"version": "1.3.0",
|
||||
"version": "1.3.1-rc.1",
|
||||
"author": {
|
||||
"name": "Steve Yegge",
|
||||
"url": "https://github.com/steveyegge"
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue