ZSDev/obsidian-connor

Watch

Fork 0

Card 464 is done: the plugin now says 0.4.2 in all four places that carry the version. (+0/−0, +0 mod) #26

Merged

Connor merged 1 commit from build/02f21fb6 into main

2026-10-25 22:25:12 +00:00

Connor commented

2026-10-25 22:22:22 +00:00

Owner

What changed

config: 4 files (+6/−5)

build/02f21fb6 → main — 4 file(s), +6/−5.

other: 4 file(s), +6/−5

⚠ This diff does not match the request (quoted below):

No source changes — the request asked for a fix, and this diff changes only other.

No test changes — the request mentions tests.

manifest.json
package-lock.json
package.json
versions.json

Growth

source: +0/−0 (net +0; budget +600)
modules: +0/−0 (budget +1)
test files added: 0; migrations: 0; evidence (screenshot/capture, not source): 0; not counted: 1
within budget

Why

Card 464 is done: the plugin now says 0.4.2 in all four places that carry the version. Once this merges, Connor's publisher builds it from main and offers it at GET /vault/plugin, so vaults on 0.4.1 will see it as newer and install it. No tag or release step is needed. The whole gate passed: 293 tests, 0 failures.

What changed

manifest.json: 0.4.1 → 0.4.2. This is what the publisher serves and what the updater on the vault side compares against.
package.json: 0.4.1 → 0.4.2. The build stamps this version into main.js, and the gate fails if it differs from manifest.json.
package-lock.json: both 0.4.1 entries (the top level and packages[""]) → 0.4.2. You didn't name this file, but it carries the version too, and leaving it at 0.4.1 would leave the lockfile out of step.
versions.json: added "0.4.2": "1.5.0" and kept every older entry. The gate fails if the manifest's version has no entry here.

Nothing else changed. The tests mention 0.4.1 in three places (test/stubs/plugin.ts, test/settings.test.ts, test/api.test.ts), but those are fake manifests the tests build for themselves, not the repo's real version. Nothing pins the real version, so I didn't touch any test.

Why no tag or release is needed […]

Gate

npm run gate ran 293 tests in 4.4s and exited 0 — green.

Flow engine

⚠ Not reviewed by the flow engine. The engine errored, so this change took the direct path: no flow engine command is set (flow.route_command)

Built by Connor's frontend backburner (dispatch 02f21fb6) in an isolated clone; shipped deterministically by ship.py. The full build notes were spoken in conversation and stored in memory (agent-dispatch:02f21fb6). Review is the gate.

The brief this build was given

Kept for provenance. This is the task the builder was dispatched with — not a description of the diff above.

Requested: Card 464. Bump the plugin version from 0.4.1 to 0.4.2 so the in-plugin self-updater (src/lib/update.ts checkOffer/isNewer, GET /vault/plugin) offers the card 463 token fix to vaults already running the older 0.4.1. Update manifest.json, and package.json and versions.json if they exist and carry the version. Check how the release/publish workflow derives the version it serves and make sure it will serve 0.4.2 after merge; if a tag or release step is needed, say exactly what. Add or adjust a test only if one pins the version. Change nothing else.

### What changed config: 4 files (+6/−5) `build/02f21fb6` → `main` — 4 file(s), +6/−5. - **other**: 4 file(s), +6/−5 > ⚠ **This diff does not match the request** (quoted below): > - No source changes — the request asked for a fix, and this diff changes only other. > - No test changes — the request mentions tests. - `manifest.json` - `package-lock.json` - `package.json` - `versions.json` ### Growth - source: +0/−0 (net +0; budget +600) - modules: +0/−0 (budget +1) - test files added: 0; migrations: 0; evidence (screenshot/capture, not source): 0; not counted: 1 - within budget ### Why Card 464 is done: the plugin now says 0.4.2 in all four places that carry the version. Once this merges, Connor's publisher builds it from main and offers it at `GET /vault/plugin`, so vaults on 0.4.1 will see it as newer and install it. No tag or release step is needed. The whole gate passed: 293 tests, 0 failures. ## What changed - **`manifest.json`**: `0.4.1` → `0.4.2`. This is what the publisher serves and what the updater on the vault side compares against. - **`package.json`**: `0.4.1` → `0.4.2`. The build stamps this version into `main.js`, and the gate fails if it differs from `manifest.json`. - **`package-lock.json`**: both `0.4.1` entries (the top level and `packages[""]`) → `0.4.2`. You didn't name this file, but it carries the version too, and leaving it at 0.4.1 would leave the lockfile out of step. - **`versions.json`**: added `"0.4.2": "1.5.0"` and kept every older entry. The gate fails if the manifest's version has no entry here. Nothing else changed. The tests mention `0.4.1` in three places (`test/stubs/plugin.ts`, `test/settings.test.ts`, `test/api.test.ts`), but those are fake manifests the tests build for themselves, not the repo's real version. Nothing pins the real version, so I didn't touch any test. ## Why no tag or release is needed […] ### Gate `npm run gate` ran 293 tests in 4.4s and exited 0 — green. ### Flow engine > ⚠ **Not reviewed by the flow engine.** The engine errored, so this change took the direct path: no flow engine command is set (flow.route_command) Built by Connor's frontend backburner (dispatch `02f21fb6`) in an isolated clone; shipped deterministically by `ship.py`. The full build notes were spoken in conversation and stored in memory (`agent-dispatch:02f21fb6`). Review is the gate. --- ### The brief this build was given _Kept for provenance. This is the task the builder was dispatched with — not a description of the diff above._ > Requested: Card 464. Bump the plugin version from 0.4.1 to 0.4.2 so the in-plugin self-updater (src/lib/update.ts checkOffer/isNewer, GET /vault/plugin) offers the card 463 token fix to vaults already running the older 0.4.1. Update manifest.json, and package.json and versions.json if they exist and carry the version. Check how the release/publish workflow derives the version it serves and make sure it will serve 0.4.2 after merge; if a tag or release step is needed, say exactly what. Add or adjust a test only if one pins the version. Change nothing else.

Joel was assigned by Connor

2026-10-25 22:22:22 +00:00

Connor added 1 commit

2026-10-25 22:22:22 +00:00

build: Card 464. Bump the plugin version from 0.4.1 to 0.4.2 so the in-plugin…

connor/growth lines 5,360 · headroom 163 of 400

gate / gate (pull_request) Successful in 9s

Details

153e24a15a

Card 464. Bump the plugin version from 0.4.1 to 0.4.2 so the in-plugin self-updater (src/lib/update.ts checkOffer/isNewer, GET /vault/plugin) offers the card 463 token fix to vaults already running the older 0.4.1. Update manifest.json, and package.json and versions.json if they exist and carry the version. Check how the release/publish workflow derives the version it serves and make sure it will serve 0.4.2 after merge; if a tag or release step is needed, say exactly what. Add or adjust a test only if one pins the version. Change nothing else.

Built by my frontend backburner (dispatch 02f21fb6), diff verified by git; shipped by ship.py. Nothing merges without review.

Connor requested review from reviewer-bot

2026-10-25 22:22:23 +00:00

reviewer-bot approved these changes

2026-10-25 22:24:31 +00:00

reviewer-bot left a comment

Independent review — reviewer-bot (local model qwen2.5-coder:14b)

The PR updates the version in four files as requested, but it does not match the stated intent of fixing something. Additionally, there are no test changes.

Suggestions (non-blocking)

suggestion <none> — The PR title and body indicate that the version should be updated in four files, but they also mention that a fix is needed. The diff only shows changes to version numbers without any actual fixes.
suggestion <none> — The PR body states that no test changes are needed, but it does not provide any explanation for why tests were not updated or added.

**Independent review — reviewer-bot (local model `qwen2.5-coder:14b`)** The PR updates the version in four files as requested, but it does not match the stated intent of fixing something. Additionally, there are no test changes. ### Suggestions (non-blocking) - suggestion `<none>` — The PR title and body indicate that the version should be updated in four files, but they also mention that a fix is needed. The diff only shows changes to version numbers without any actual fixes. - suggestion `<none>` — The PR body states that no test changes are needed, but it does not provide any explanation for why tests were not updated or added.

Connor merged commit 675ab31f6b into main

2026-10-25 22:25:12 +00:00

Connor deleted branch build/02f21fb6

2026-10-25 22:25:13 +00:00

Connor referenced this pull request from a commit

2026-10-25 22:25:14 +00:00

Merge pull request 'Card 464 is done: the plugin now says 0.4.2 in all four places that carry the version. (+0/−0, +0 mod)' (#26) from build/02f21fb6 into main