mirror of
https://github.com/blamouche/obsidian-any-ai-code.git
synced 2026-07-22 06:53:38 +00:00
Open feature/automation branch and bump to 0.2.0
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
8efbce2156
commit
366733dadd
4 changed files with 21 additions and 1 deletions
|
|
@ -65,3 +65,4 @@
|
|||
| 2026-04-27 09:05:00 CEST | agent | Reworded plugin description in `manifest.json` and `package.json` to surface the "AI assistant CLI" concept (per user request). Validated 6 candidates against `evaluateSentenceCase` from `eslint-plugin-obsidianmd@0.2.4`, picked the 106-char variant `Run an AI assistant CLI like Claude from a right sidebar terminal panel, with a customizable runtime list.` Bumped to 0.1.45. | `manifest.json`, `package.json`, `versions.json`, `package-lock.json`, `.prompt-hub/version.md`, `.prompt-hub/releases.md` | success | Commit, push, annotated tag 0.1.45. |
|
||||
| 2026-04-27 23:09:00 CEST | agent | User reported the community-store auto-install only ships `main.js`, `manifest.json`, `styles.css`, which doesn't include the `pty-proxy.js` / `pty-bridge.py` files the plugin spawns. Fix: embedded both auxiliary file contents into `main.js` at build time via esbuild `define` (`PTY_PROXY_SOURCE`, `PTY_BRIDGE_SOURCE` constants declared in main.ts), and added `ensureProxyFiles(pluginDir)` that writes them lazily before each `spawnPtyProxy` call (only when missing or content drift). Verified embedded markers (`spawnPythonBridge`, `decode_payload`, `TIOCSWINSZ`, `pty.fork`) present in built main.js. README `Required files` reworked accordingly. Bumped to 0.1.46. | `esbuild.config.mjs`, `main.ts`, `main.js`, `manifest.json`, `versions.json`, `package.json`, `package-lock.json`, `README.md`, `.prompt-hub/version.md`, `.prompt-hub/releases.md` | success | Commit, push, annotated tag 0.1.46. User republishes draft so community-store install works for new users. |
|
||||
| 2026-05-12 23:12:00 CEST | agent | Trimmed the release zip staging step to the 3 canonical Obsidian plugin files (`manifest.json`, `main.js`, `styles.css`). The auxiliary `pty-proxy.js` / `pty-bridge.py` are now embedded in main.js so they no longer need to ship; `versions.json`, `package.json`, `package-lock.json` also dropped from the zip (`versions.json` stays as a standalone release asset since Obsidian fetches it directly from the release URL). Updated release notes body + README `Release` and `Required files` sections. Dry-run zip listing confirmed 3 files in the `any-ai-cli/` folder. Bumped to 0.1.47. | `.github/workflows/release.yml`, `README.md`, `manifest.json`, `versions.json`, `package.json`, `package-lock.json`, `.prompt-hub/version.md`, `.prompt-hub/releases.md` | success | Commit, push, annotated tag 0.1.47. |
|
||||
| 2026-05-19 22:34:08 CEST | agent | Created new branch `feature/automation` from `main` for upcoming automation work; bumped minor version 0.1.48 → 0.2.0 per Prompt Hub branch protocol and logged the release entry. | `git checkout -b feature/automation`, `.prompt-hub/version.md`, `.prompt-hub/releases.md`, `.prompt-hub/todo/todo-20260519-223408-create-feature-automation-branch.md` | success | Commit the version/releases bump on `feature/automation` and push the new branch upstream. |
|
||||
|
|
|
|||
|
|
@ -1,5 +1,8 @@
|
|||
# Releases
|
||||
|
||||
## 0.2.0 - 2026-05-19
|
||||
- Opened branch `feature/automation` off `main` for upcoming automation work; bumped minor version per Prompt Hub branch protocol.
|
||||
|
||||
## 0.1.48 - 2026-05-12
|
||||
- Trimmed the release zip down to the three canonical Obsidian plugin files (`manifest.json`, `main.js`, `styles.css`) — the auxiliary `pty-proxy.js` and `pty-bridge.py` sources are already embedded in `main.js` (since 0.1.46) and written at runtime, so they no longer need to ship alongside the zip. `versions.json` and the `package.json` / `package-lock.json` pair are also dropped from the zip; `versions.json` stays as a standalone release asset (Obsidian fetches it directly).
|
||||
- Reworked the release notes body to lead with the community-store install path, document the embedded-source bootstrap, and clearly list what ships where (zip vs standalone assets vs repo-only).
|
||||
|
|
|
|||
|
|
@ -0,0 +1,16 @@
|
|||
# Task: Create branch `feature/automation`
|
||||
|
||||
## Objective
|
||||
Create a new git branch `feature/automation` off `main` for upcoming automation work, applying the Prompt Hub branch protocol (minor version bump, releases log, memory log).
|
||||
|
||||
## Plan
|
||||
1. Verify working tree is clean and `main` is up to date with origin.
|
||||
2. Create branch `feature/automation` from `main` and switch to it.
|
||||
3. Bump `.prompt-hub/version.md` from `0.1.48` to `0.2.0` (new branch → minor bump).
|
||||
4. Add a `0.2.0` entry to `.prompt-hub/releases.md` noting the new branch.
|
||||
5. Append a memory log entry for this action.
|
||||
6. Commit the version/releases bump on the new branch.
|
||||
7. Push the branch to `origin` with upstream tracking.
|
||||
|
||||
## Review
|
||||
- _to be filled in after execution_
|
||||
|
|
@ -1 +1 @@
|
|||
0.1.48
|
||||
0.2.0
|
||||
|
|
|
|||
Loading…
Reference in a new issue