backlog.md-darwin-arm64 1.47.1 → 1.49.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +160 -68
  2. package/backlog +0 -0
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -1,8 +1,20 @@
1
+ <p align="center">
2
+ <img src="./.github/backlog-logo.png" alt="Backlog.md logo" width="120">
3
+ </p>
4
+
1
5
  <h1 align="center">Backlog.md</h1>
2
- <p align="center">Markdown‑native Task Manager &amp; Kanban visualizer for any Git repository</p>
6
+ <p align="center"><strong>Markdown‑native Task Manager &amp; Kanban visualizer for any Git repository</strong></p>
7
+ <p align="center">AI agents write the code. You review the tasks: before, during, and after.</p>
8
+
9
+ <p align="center">
10
+ <a href="https://www.npmjs.com/package/backlog.md"><img src="https://img.shields.io/npm/v/backlog.md?color=brightgreen" alt="npm version"></a>
11
+ <a href="https://www.npmjs.com/package/backlog.md"><img src="https://img.shields.io/npm/dm/backlog.md" alt="npm downloads"></a>
12
+ <a href="https://github.com/MrLesk/Backlog.md/blob/main/LICENSE"><img src="https://img.shields.io/github/license/MrLesk/Backlog.md" alt="MIT license"></a>
13
+ <a href="https://github.com/MrLesk/Backlog.md"><img src="https://img.shields.io/github/stars/MrLesk/Backlog.md?style=social" alt="GitHub stars"></a>
14
+ </p>
3
15
 
4
16
  <p align="center">
5
- <code>npm i -g backlog.md</code> or <code>bun add -g backlog.md</code> or <code>brew install backlog-md</code> or <code>nix run github:MrLesk/Backlog.md</code>
17
+ <code>npm i -g backlog.md</code>
6
18
  </p>
7
19
 
8
20
  ![Backlog demo GIF using: backlog board](./.github/backlog-v1.40.gif)
@@ -10,32 +22,53 @@
10
22
 
11
23
  ---
12
24
 
13
- > **Backlog.md** turns any folder with a Git repo into a **self‑contained project board**
25
+ > **Backlog.md** turns any folder into a **self‑contained project board**
14
26
  > powered by plain Markdown files and a zero‑config CLI.
15
- > Built for **spec‑driven AI development** — structure your tasks so AI agents deliver predictable results.
16
27
 
17
- ## Features
28
+ ## Why Backlog.md in the AI era
18
29
 
19
- * 📝 **Markdown-native tasks** -- manage every issue as a plain `.md` file
30
+ AI agents can now produce more plausible code in an hour than you can carefully read in a day.
31
+ The bottleneck is no longer writing code. It's your attention. You can't meaningfully review
32
+ 15,000 generated lines in one sitting, but you can read a screenful of task specs with acceptance
33
+ criteria before any code exists, and push back while a misunderstanding is still one sentence,
34
+ not a rebuilt feature.
20
35
 
21
- * 🤖 **AI-Ready** -- Works with Claude Code, Gemini CLI, Codex, Kiro & any other MCP or CLI compatible AI assistants
36
+ Backlog.md structures agent work around **three review checkpoints**:
22
37
 
23
- * 📊 **Instant terminal Kanban** -- `backlog board` paints a live board in your shell
38
+ 1. **Review the spec:** the agent decomposes your idea into tasks with descriptions, acceptance
39
+ criteria, and milestones before implementation starts.
40
+ 2. **Review the plan:** the agent researches your codebase and writes its implementation plan
41
+ into the task. Approve it or steer before any code is written.
42
+ 3. **Review the code:** one task = one context window = one PR. Diffs stay a size a human can
43
+ actually read.
24
44
 
25
- * 🌐 **Modern web interface** -- `backlog browser` launches a sleek web UI for visual task management
45
+ Afterwards, the completed tasks remain in Git as a permanent record of what was attempted and why,
46
+ legible to you, your team, and the next agent.
26
47
 
27
- * 🔍 **Powerful search** -- fuzzy search across tasks, docs & decisions with `backlog search`
48
+ **Dogfooded:** nearly all of Backlog.md's own code is written by AI agents working through
49
+ Backlog.md itself. The full task ledger lives in this repo's [backlog folder](backlog/tasks).
28
50
 
29
- * 📋 **Rich query commands** -- view, list, filter, or archive tasks with ease
30
- * ✅ **Definition of Done defaults** -- add a reusable checklist to every new task
51
+ 📺 **See it in action:** [Devoxx Belgium 2025](https://www.youtube.com/watch?v=LSoDQU_9MMA) · [AI Engineer Code Summit 2025](https://www.youtube.com/watch?v=zMXKhhwiCIc)
31
52
 
32
- * 📤 **Board export** -- `backlog board export` creates shareable markdown reports
53
+ ## Features
33
54
 
34
- * 🔒 **100 % private & offline** -- backlog lives entirely inside your repo and you can manage everything locally
55
+ * 🤖 **AI-ready** -- works with Claude Code, Gemini CLI, Codex, Kiro & any other MCP or CLI compatible AI assistant
35
56
 
36
- * 💻 **Cross-platform** -- runs on macOS, Linux, and Windows
57
+ * 📝 **Markdown-native tasks** -- every task is a plain `.md` file in your repo
37
58
 
38
- * 🆓 **MIT-licensed & open-source** -- free for personal or commercial use
59
+ * ✅ **Acceptance criteria & Definition of Done** -- verifiable scope per task, plus a reusable DoD checklist for every new task
60
+
61
+ * 🎯 **Milestones & dependencies** -- structure bigger efforts and make execution order reviewable
62
+
63
+ * 📊 **Terminal Kanban** -- `backlog board` paints a live board in your shell; `backlog board export` creates shareable markdown reports
64
+
65
+ * 🌐 **Web UI** -- `backlog browser` serves a local Kanban board with drag-and-drop and task editing forms
66
+
67
+ * 🔍 **Search** -- fuzzy search across tasks, docs & decisions with `backlog search`
68
+
69
+ * 🔒 **Local-first** -- no server, no account, no telemetry; tasks are plain files in your repo, and remote Git operations are optional
70
+
71
+ * 💻 Cross-platform (macOS, Linux, Windows) · 🆓 MIT-licensed & open-source
39
72
 
40
73
 
41
74
  ---
@@ -44,9 +77,10 @@
44
77
 
45
78
  ```bash
46
79
  # Install
47
- bun i -g backlog.md
48
- # or: npm i -g backlog.md
80
+ npm i -g backlog.md
81
+ # or: bun add -g backlog.md
49
82
  # or: brew install backlog-md
83
+ # or: nix run github:MrLesk/Backlog.md
50
84
 
51
85
  # Initialize in any Git repo
52
86
  backlog init "My Awesome Project"
@@ -55,48 +89,74 @@ backlog init "My Awesome Project"
55
89
  backlog init "Personal Planning" --no-git
56
90
  ```
57
91
 
92
+ > [!TIP]
93
+ > **Running one-off with `npx`?** This tool's npm package is named `backlog.md`, so use the full name: `npx backlog.md init "My Project"`, `npx backlog.md board`.
94
+ > Without an install, `npx backlog` resolves to an unrelated third-party npm package — not this tool.
95
+ > (With `backlog.md` installed as a project dependency, `npx backlog` runs the local binary as usual.)
96
+
97
+ ### Run with Nix
98
+
99
+ Run Backlog.md directly from the repository flake:
100
+
101
+ ```bash
102
+ nix run github:MrLesk/Backlog.md -- --version
103
+ ```
104
+
105
+ Or install the named package into your Nix profile:
106
+
107
+ ```bash
108
+ nix profile install github:MrLesk/Backlog.md#backlog-md
109
+ ```
110
+
111
+ The Nix flake supports `x86_64-linux`, `aarch64-linux`, and
112
+ `aarch64-darwin`. The x86_64 Linux package uses Bun's baseline runtime so it
113
+ also works on pre-AVX2 processors with AVX support. Intel macOS users can use
114
+ the npm, Bun, or Homebrew installation instead.
115
+
58
116
  The init wizard will ask how you want to connect AI tools:
59
- - **CLI instructions** (recommended) — creates a short instruction file that tells agents to run `backlog instructions overview`.
60
- - **MCP connector** — optionally auto-configures Claude Code, Codex, Gemini CLI, Kiro or Cursor for teams that prefer MCP.
61
- - **Skip** — no AI setup; use Backlog.md purely as a task manager.
117
+ - **CLI instructions** (recommended): creates a short instruction file that tells agents to run `backlog instructions overview`.
118
+ - **MCP connector**: optionally auto-configures Claude Code, Codex, Gemini CLI, Kiro or Cursor for teams that prefer MCP.
119
+ - **Skip**: no AI setup; use Backlog.md purely as a task manager.
120
+
121
+ For Cursor with CLI instructions, select AGENTS.md or pass `--agent-instructions cursor`; both use the same AGENTS.md target. Backlog.md preserves existing AGENTS.md content and does not migrate or remove unrelated user-managed `.cursor/rules` files.
62
122
 
63
- Backlog data is stored in a project-local backlog folder such as `backlog/`, `.backlog/`, or a custom project-relative path configured through `backlog.config.yml`. Tasks remain human-readable Markdown files (e.g. `task-10 - Add core search functionality.md`). Git is optional: `backlog init --no-git` creates a filesystem-only project and disables cross-branch checks, remote operations, and auto-commit.
123
+ Everything is stored as human-readable Markdown in a project-local backlog folder such as `backlog/`, `.backlog/`, or a custom project-relative path configured through `backlog.config.yml` (e.g. `task-10 - Add core search functionality.md`). Task IDs use a configurable prefix (`backlog init --task-prefix`): the default produces `TASK-1`-style IDs, while this repository uses `back`, so examples below show `BACK-1`-style IDs. Git is optional: `backlog init --no-git` creates a filesystem-only project.
64
124
 
65
125
  ---
66
126
 
67
- ### Working with AI agents
127
+ ## Working with AI agents
68
128
 
69
- This is the recommended flow for Claude Code, Codex, Gemini CLI, Kiro and similar tools — following the **spec‑driven AI development** approach.
129
+ This is the recommended flow for Claude Code, Codex, Gemini CLI, Kiro and similar tools, following the **spec‑driven AI development** approach.
70
130
  After running `backlog init`, agents should start by running `backlog instructions overview`. Work in this loop:
71
131
 
72
- **Step 1 — Describe your idea.** Tell the agent what you want to build and ask it to split the work into small tasks with clear descriptions and acceptance criteria.
132
+ **Step 1: Describe your idea.** Tell the agent what you want to build and ask it to split the work into small tasks with clear descriptions and acceptance criteria.
73
133
 
74
134
  **🤖 Ask your AI Agent:**
75
135
  > I want to add a search feature to the web view that searches tasks, docs, and decisions. Please decompose this into small Backlog.md tasks.
76
136
 
77
137
  > [!NOTE]
78
- > **Review checkpoint #1** — read the task descriptions and acceptance criteria.
138
+ > **Review checkpoint #1:** read the task descriptions and acceptance criteria.
79
139
 
80
- **Step 2 — One task at a time.** Work on a single task per agent session, one PR per task. Good task splitting means each session can work independently without conflicts. Make sure each task is small enough to complete in a single conversation. You want to avoid running out of context window.
140
+ **Step 2: One task at a time.** Work on a single task per agent session, one PR per task. Good task splitting means each session can work independently without conflicts. Make sure each task is small enough to complete in a single conversation. You want to avoid running out of context window.
81
141
 
82
- **Step 3 — Plan before coding.** Ask the agent to research and write an implementation plan in the task. Do this right before implementation so the plan reflects the current state of the codebase.
142
+ **Step 3: Plan before coding.** Ask the agent to research and write an implementation plan in the task. Do this right before implementation so the plan reflects the current state of the codebase.
83
143
 
84
144
  **🤖 Ask your AI Agent:**
85
145
  > Work on BACK-10 only. Research the codebase and write an implementation plan in the task. Wait for my approval before coding.
86
146
 
87
147
  > [!NOTE]
88
- > **Review checkpoint #2** — read the plan. Does the approach make sense? Approve it or ask the agent to revise.
148
+ > **Review checkpoint #2:** read the plan. Does the approach make sense? Approve it or ask the agent to revise.
89
149
 
90
- **Step 4 — Implement and verify.** Let the agent implement the task.
150
+ **Step 4: Implement and verify.** Let the agent implement the task.
91
151
 
92
152
  > [!NOTE]
93
- > **Review checkpoint #3** — review the code, run tests, check linting, and verify the results match your expectations.
153
+ > **Review checkpoint #3:** review the code, run tests, check linting, and verify the results match your expectations.
94
154
 
95
155
  If the output is not good enough: clear the plan/notes/final summary, refine the task description and acceptance criteria, and run the task again in a fresh session.
96
156
 
97
157
  ---
98
158
 
99
- ### Working without AI agents
159
+ ## Working without AI agents
100
160
 
101
161
  Use Backlog.md as a standalone task manager from the terminal or browser.
102
162
 
@@ -107,6 +167,7 @@ backlog task edit BACK-1 -d "Detailed context" --ac "Clear acceptance criteria"
107
167
 
108
168
  # Track work
109
169
  backlog task list -s "To Do"
170
+ backlog task list --json | jq '.tasks[] | .id'
110
171
  backlog task edit BACK-1 --comment "Can we split the UI work into a separate PR?" --comment-author @sara
111
172
  backlog search "kanban"
112
173
  backlog board
@@ -115,7 +176,9 @@ backlog board
115
176
  backlog browser
116
177
  ```
117
178
 
118
- You can switch between AI-assisted and manual workflows at any time — both operate on the same Markdown task files. It is recommended to modify tasks via Backlog.md commands (CLI/MCP/Web) rather than editing task files manually, so field types and metadata stay consistent. Tasks can record project-root-relative modified files and later be found with `backlog search --modified-file src/path.ts --plain`. Use task comments for discussion and review notes; comment bodies may contain Markdown, but standalone `---` lines are reserved as comment delimiters. Use Implementation Notes for execution progress and Final Summary for completion notes.
179
+ You can switch between AI-assisted and manual workflows at any time; both operate on the same Markdown task files. Just prefer Backlog.md commands (CLI/MCP/Web) over hand-editing task files, so field types and metadata stay consistent.
180
+
181
+ Read commands support stable, versioned JSON for scripts and integrations. Use `--json` with `task list`, `task view`, the `task <id>` shorthand, and `search`. JSON mode is noninteractive and keeps successful stdout machine-readable.
119
182
 
120
183
  **Learn more:** [CLI reference](CLI-INSTRUCTIONS.md) | [Advanced configuration](ADVANCED-CONFIG.md)
121
184
 
@@ -123,7 +186,8 @@ You can switch between AI-assisted and manual workflows at any time — both ope
123
186
 
124
187
  ## <img src="./.github/web-interface-256.png" alt="Web Interface" width="28" height="28" align="center"> Web Interface
125
188
 
126
- Launch a modern, responsive web interface for visual task management:
189
+ Launch a web interface for visual task management on the local machine. The server listens on `127.0.0.1` and is not
190
+ reachable from other devices on the LAN or VPN:
127
191
 
128
192
  ```bash
129
193
  # Start the web server (opens browser automatically)
@@ -138,7 +202,7 @@ backlog browser --no-open
138
202
 
139
203
  **Features:**
140
204
  - Interactive Kanban board with drag-and-drop
141
- - Task creation and editing with rich forms
205
+ - Task creation and editing with forms
142
206
  - Interactive acceptance criteria editor with checklists
143
207
  - Real-time updates across all views
144
208
  - Responsive design for desktop and mobile
@@ -194,9 +258,17 @@ You can run `backlog init` (even if you already initialized Backlog.md) and choo
194
258
 
195
259
  </details>
196
260
 
197
- Use the shared `backlog` server name everywhere. The server finds the active project from your client's MCP roots, and re-resolves when you switch workspace or worktree. Until it finds one, it serves `backlog://init-required`. A single user-scope server covers every repo.
261
+ <details>
262
+ <summary><strong>Cursor / other MCP clients</strong></summary>
263
+
264
+ Use the manual JSON config below in your client's MCP settings.
265
+
266
+ </details>
267
+
268
+ Use the shared `backlog` server name everywhere. The server finds the active project from your client's MCP roots, and re-resolves when you switch workspace or worktree. A single user-scope server covers every repo.
198
269
 
199
- ### Manual config
270
+ <details>
271
+ <summary><strong>Manual config</strong></summary>
200
272
 
201
273
  ```json
202
274
  {
@@ -214,6 +286,9 @@ Use the shared `backlog` server name everywhere. The server finds the active pro
214
286
 
215
287
  Set `BACKLOG_CWD` to pin the server to one project and stop workspace following. Use it to always target the same backlog, or when your client can't report MCP roots.
216
288
  If your IDE supports custom args but not env vars, you can also use `["mcp", "start", "--cwd", "/absolute/path/to/your/project"]`.
289
+ Until the server finds an initialized project, it serves `backlog://init-required`.
290
+
291
+ </details>
217
292
 
218
293
  > [!IMPORTANT]
219
294
  > When adding the MCP server manually, add a short instruction to your CLAUDE.md/AGENTS.md files telling agents to read `backlog://workflow/overview`.
@@ -228,7 +303,7 @@ Use `/mcp` command in your AI tool (Claude Code, Codex, Kiro) to verify if the c
228
303
 
229
304
  ## <img src="./.github/cli-reference-256.png" alt="CLI Reference" width="28" height="28" align="center"> CLI reference
230
305
 
231
- Full command reference — task management, search, board, docs, decisions, and more: **[CLI-INSTRUCTIONS.md](CLI-INSTRUCTIONS.md)**
306
+ Full command reference covering task management, search, board, docs, decisions, and more: **[CLI-INSTRUCTIONS.md](CLI-INSTRUCTIONS.md)**
232
307
 
233
308
  Quick examples: `backlog`, `backlog instructions`, `backlog task create`, `backlog task list`, `backlog task edit`, `backlog milestone add`, `backlog milestone rename`, `backlog milestone remove`, `backlog search`, `backlog board`, `backlog browser`.
234
309
 
@@ -238,34 +313,11 @@ Full help: `backlog --help`
238
313
 
239
314
  ## <img src="./.github/configuration-256.png" alt="Configuration" width="28" height="28" align="center"> Configuration
240
315
 
241
- Backlog.md merges the following layers (highest → lowest):
242
-
243
- 1. CLI flags
244
- 2. Project config file:
245
- - `backlog.config.yml` when present
246
- - otherwise `backlog/config.yml` or `.backlog/config.yml`
247
- 3. Built‑ins
248
-
249
- ### Interactive wizard (`backlog config`)
316
+ Backlog.md works with zero configuration. Settings merge from CLI flags, then the project config file (`backlog.config.yml` when present, otherwise `backlog/config.yml` or `.backlog/config.yml`), then built‑in defaults.
250
317
 
251
- Run `backlog config` with no arguments to launch the full interactive wizard. This is the same experience triggered from `backlog init` when you opt into advanced settings, and it walks through the complete configuration surface:
252
- - Cross-branch accuracy: `checkActiveBranches`, `remoteOperations`, and `activeBranchDays`.
253
- - Git workflow: `autoCommit` and `bypassGitHooks`.
254
- - ID formatting: enable or size `zeroPaddedIds`.
255
- - Editor integration: pick a `defaultEditor` with availability checks.
256
- - Definition of Done defaults: interactively add/remove/reorder/clear project-level `definition_of_done` checklist items.
257
- - Web UI defaults: choose `defaultPort` and whether `autoOpenBrowser` should run.
318
+ Run `backlog config` with no arguments to launch the interactive wizard (the same experience triggered from `backlog init` advanced setup). It walks through cross-branch accuracy (`checkActiveBranches`, `remoteOperations`, `activeBranchDays`), Git workflow (`autoCommit`, `bypassGitHooks`), ID formatting (`zeroPaddedIds`), editor integration (`defaultEditor`), Definition of Done defaults, and Web UI defaults (`defaultPort`, `autoOpenBrowser`). Skipping the wizard applies the safe built-in defaults, and rerunning `backlog init` or `backlog config` pre-populates prompts with your current values.
258
319
 
259
- Skipping the wizard (answering "No" during init) applies the safe defaults that ship with Backlog.md:
260
- - `checkActiveBranches=true`, `remoteOperations=true`, `activeBranchDays=30`.
261
- - `autoCommit=false`, `bypassGitHooks=false`.
262
- - `zeroPaddedIds` disabled.
263
- - `defaultEditor` unset (falls back to your environment).
264
- - `defaultPort=6420`, `autoOpenBrowser=true`.
265
-
266
- For filesystem-only projects, run `backlog init --no-git`. Backlog.md will not run `git init`, and the saved config forces `checkActiveBranches=false`, `remoteOperations=false`, and `autoCommit=false` so CLI, Web, and MCP local-file workflows do not depend on a Git repository.
267
-
268
- Whenever you revisit `backlog init` or rerun `backlog config`, the wizard pre-populates prompts with your current values so you can adjust only what changed.
320
+ For filesystem-only projects (`backlog init --no-git`), the saved config forces `checkActiveBranches=false`, `remoteOperations=false`, and `autoCommit=false` so CLI, Web, and MCP local-file workflows do not depend on a Git repository.
269
321
 
270
322
  ### Definition of Done defaults
271
323
 
@@ -282,16 +334,56 @@ When a project uses root config discovery, edit `backlog.config.yml` instead of
282
334
 
283
335
  These items are added to every new task by default. You can add more on create with `--dod`, or disable defaults per task with `--no-dod-defaults`.
284
336
 
285
- For the full configuration reference (all options, commands, and detailed notes), see **[ADVANCED-CONFIG.md](ADVANCED-CONFIG.md)**.
337
+ For the full configuration reference (all options, default values, commands, and detailed notes), see **[ADVANCED-CONFIG.md](ADVANCED-CONFIG.md)**.
286
338
 
287
339
  ---
288
340
 
289
- ## 🌐 Community Tools
341
+ ## Troubleshooting
342
+
343
+ ### Apple Silicon (macOS)
344
+
345
+ On M-series Macs, `backlog` can fail with `illegal hardware instruction` or `Binary package not installed for darwin-...` when Node, Bun, or Homebrew run under Rosetta (x64 emulation) and install the Intel binary instead of the arm64 one — or the other way around. The launcher runs whichever darwin variant (arm64 or x64) is actually installed, but a clean native-arch install is the reliable fix.
346
+
347
+ Check what your tools report:
348
+
349
+ ```bash
350
+ uname -m # arm64 = Apple Silicon hardware; x86_64 = Intel or a Rosetta shell
351
+ node -p process.arch # architecture of your Node/Bun runtime
352
+ sysctl -in sysctl.proc_translated # 1 = current shell runs under Rosetta
353
+ which brew # /opt/homebrew = arm64 brew, /usr/local = Intel brew
354
+ ```
355
+
356
+ If the architectures disagree, reinstall with the native one:
357
+
358
+ ```bash
359
+ # Homebrew: make sure `which brew` prints /opt/homebrew, then
360
+ brew reinstall backlog-md
361
+
362
+ # npm
363
+ arch -arm64 npm i -g backlog.md
364
+
365
+ # Bun
366
+ arch -arm64 bun add -g backlog.md
367
+ ```
368
+
369
+ Running an x64 Node under Rosetta on purpose also works: `backlog` falls back to whichever `backlog.md-darwin-*` package is present.
370
+
371
+ ---
372
+
373
+ ## 📺 Talks & Community
374
+
375
+ Watch Backlog.md in action:
376
+
377
+ - **Devoxx Belgium 2025**: [the spec-driven agent workflow behind Backlog.md, live on stage](https://www.youtube.com/watch?v=LSoDQU_9MMA)
378
+ - **AI Engineer Code Summit 2025**: [Backlog.md: task management for AI agents](https://www.youtube.com/watch?v=zMXKhhwiCIc)
379
+ - Slides from these and more talks: [mrlesk.com/talks](https://mrlesk.com/talks)
380
+
381
+ ### Community tools
290
382
 
291
383
  - **[vscode-backlog-md](https://marketplace.visualstudio.com/items?itemName=ysamlan.vscode-backlog-md)** - VS Code extension with issues panel, kanban view, and editing. ([ysamlan/vscode-backlog-md](https://github.com/ysamlan/vscode-backlog-md))
292
384
 
293
385
  ---
294
386
 
295
- ### License
387
+ ## License
296
388
 
297
- Backlog.md is released under the **MIT License** – do anything, just give credit. See [LICENSE](LICENSE).
389
+ Backlog.md is released under the **MIT License**: do anything, just give credit. See [LICENSE](LICENSE).
package/backlog CHANGED
Binary file
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "backlog.md-darwin-arm64",
3
- "version": "1.47.1",
3
+ "version": "1.49.0",
4
4
  "os": ["darwin"],
5
5
  "cpu": ["arm64"],
6
6
  "files": ["backlog","package.json","LICENSE"],