Skip to content

chore(release): 0.1.1 — provenance and the docs pass - #14

Merged
leemour merged 4 commits into
mainfrom
chore/version-0.1.1
Nov 17, 2026
Merged

leemour merged 4 commits into
mainfrom
chore/version-0.1.1

Conversation

@leemour

@leemour leemour commented Nov 17, 2026 •

Copy link
Copy Markdown
Member

Task

amo 0.1.1, published from GitHub Actions with npm provenance.

Why

WireCat Desktop installs a built-in tool only from a release its own repository's release.yml built (wirecat-desktop src-tauri/src/provenance.rs). 0.1.0 was published from a computer (bin/release --local), so Desktop refuses it.

What

  • Version 0.1.1 in package.json and src/version.ts, a CHANGELOG section. No code change since 0.1.0.
  • The user docs brought up to bitrix24-cli's, page by page: new MCP and permissions pages, a full start page (no separate leads, the integration's support waiver, no deal delete), setup in the README's quick start with absolute links, environment variables, 21 troubleshooting rows on amo's real error codes; the wrong "amoCRM sets the 100-a-day contact limit" fixed (it is WireCat's rule), TODO comments and future tense removed. Every command and flag named was checked against the built CLI.

Conformance

release:check

No code change since 0.1.0 (#9), whose full release:check passed; version:check passes here, CI runs the rest.

Live check

0.1.1 266bdea805d3d10e9b71a38dac193c098e80da53 2026-11-17 bin/amo-live v2:20275c533be085ded04c495661a44579a4456385334744e05bd91679bdb5cb41

bin/amo-live fashionscrew --host … --write on the test account, at the owner's request: every step passed (reads, sync, a test deal created, moved and closed as lost). The docs commits after it change no file the record hashes; cli-dev live check --version 0.1.1 passes on the tip.

Fresh audit

None new: no code change since 0.1.0's audit (#9).

🤖 Generated with Claude Code

leemour and others added 4 commits November 18, 2026 00:18
Desktop installs a built-in tool only from a release its own repository's
workflow built (npm provenance); 0.1.0 was published from a computer.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ages, a full start page, setup in the quick start

- docs/index.md follows b24's start page: what you get, things a newcomer would not guess (no leads apart from deals,
  the private integration and its support waiver, no deal delete, ask goes ahead over MCP), how it looks, why, what
  it can do, a quick start with an agent prompt, limits and a task table.
- New docs/mcp.md (add, the three tools, keeping writes yours, the browser) and docs/permissions.md (levels,
  defaults, API keys, agents and MCP, checks that hold whatever the settings say), moved out of usage and
  configuration, which now link them.
- README and installation: `amo work setup` in the quick start, no TODO comments, no "next Desktop release"
  future tense, absolute GitHub links so they work on npmjs.com, files not supported yet, close a deal as lost.
- usage, security, skill: the 100-a-day limit on other clients' phones and e-mails is amo's own, for a user who is
  not an administrator, not amoCRM's; outcome_unknown, store status and sync --rescan.
- troubleshooting: first checks, and not signed in, a duplicate sign-in, the filter add-on, the daily limit,
  access denied, employee-only refusals, rate limit and outcome unknown.
- configuration: variables (AMO_PROFILE, AMO_READ_ONLY, AMO_TOKEN with AMO_HOST, the client secret, moved folders)
  and record_input's "failed".

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@leemour leemour changed the title chore(release): 0.1.1 chore(release): 0.1.1 — provenance and the docs pass Nov 17, 2026
@leemour
leemour merged commit 7cc1841 into main Nov 17, 2026
17 of 18 checks passed
@leemour
leemour deleted the chore/version-0.1.1 branch November 17, 2026 23:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant