@michaelschnyder/teams-cli 0.2.0-canary.10.1.ge1da9b48 → 0.2.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.
@@ -1,34 +1,32 @@
1
1
  {
2
2
  "schemaVersion": 1,
3
- "version": "0.2.0-canary.10.1.ge1da9b48",
4
- "channel": "canary",
5
- "builtAt": "2026-09-04T11:46:03.515Z",
3
+ "version": "0.2.0",
4
+ "channel": "stable",
5
+ "builtAt": "2026-09-04T11:47:26.658Z",
6
6
  "source": {
7
- "branch": "codex/restore-version-upgrade",
8
- "commit": "e1da9b48a2efd78ba7ef90511bd6a15665c3f713",
9
- "commitUrl": "https://github.com/michaelschnyder/teams-cli/commit/e1da9b48a2efd78ba7ef90511bd6a15665c3f713",
10
- "pullRequest": 15,
11
- "pullRequestUrl": "https://github.com/michaelschnyder/teams-cli/pull/15",
12
- "author": "michaelschnyder"
7
+ "branch": "main",
8
+ "commit": "0f109289ab1398dbf4c8717bb91df07588a96bc0",
9
+ "commitUrl": "https://github.com/michaelschnyder/teams-cli/commit/0f109289ab1398dbf4c8717bb91df07588a96bc0",
10
+ "author": "Michael Schnyder <michael.schnyder@outlook.com>"
13
11
  },
14
12
  "trigger": {
15
- "kind": "merged-pull-request",
13
+ "kind": "release",
16
14
  "actor": "michaelschnyder"
17
15
  },
18
16
  "runner": {
19
- "name": "GitHub Actions 1000001107",
17
+ "name": "GitHub Actions 1000001109",
20
18
  "os": "Linux",
21
19
  "architecture": "X64"
22
20
  },
23
21
  "workflow": {
24
- "runId": "33869464048",
25
- "runNumber": "10",
22
+ "runId": "33869547336",
23
+ "runNumber": "11",
26
24
  "runAttempt": "1",
27
- "url": "https://github.com/michaelschnyder/teams-cli/actions/runs/33869464048"
25
+ "url": "https://github.com/michaelschnyder/teams-cli/actions/runs/33869547336"
28
26
  },
29
27
  "releaseNotes": {
30
- "title": "Restore safe CLI self-upgrades",
31
- "body": "## Summary\n\n- restore `teams-cli version --upgrade` for verified global npm installations on stable and canary channels\n- restore interactive update offers and make `version --channel stable|canary` install the selected channel before persisting it\n- refuse all installer mutations for npx, project-local packages, source checkouts, and installations not owned by the active npm global root\n- keep snapshots pinned for ordinary upgrades while allowing an explicit channel switch to leave a globally installed snapshot\n- refresh managed skills through the newly installed CLI and retain precise partial-failure reporting\n\n## Why it was removed\n\nThe previous updater always ran `npm install --global`, even if the running CLI came from a project dependency or another package-manager scope. Review correctly identified that this could create or replace an unrelated global installation. The feature was then removed entirely.\n\nThis change preserves that safety concern by resolving npm's active global root and requiring the running package to match its exact `@michaelschnyder/teams-cli` path before npm is allowed to change anything.\n\n## Verification\n\n- `npm run check`\n- `CI=true npm test` (115 tests)\n- `npm run build`\n- `npm run package:check`\n- `npm run package:smoke`\n",
32
- "url": "https://github.com/michaelschnyder/teams-cli/pull/15"
28
+ "title": "Teams CLI v0.2.0",
29
+ "body": "## Highlights\n\n### Create workspace safeguards visually\n\n`teams-cli policy edit --open` now launches a local policy editor where you can choose which people, group chats, and channels may be read or posted to. You can review the generated policy, save a draft, and activate it when ready.\n\nRead and post access are configured independently, explicit denials take priority, and overlapping active policies can only narrow access. The editor keeps Teams credentials and message content out of the browser UI.\n\n### Get started with fewer identifiers and commands\n\n- `teams-cli login` signs in and discovers the default tenant and user automatically. Most users no longer need to provide tenant IDs, user IDs, or named profiles.\n- `teams-cli message send --person alice@example.com --body \"Hello\"` can find or start a direct conversation without requiring you to discover a chat ID first.\n- `teams-cli chat search \"Alice\" --json` uses bounded, server-ranked search instead of downloading your complete chat collection.\n\n### Set up coding agents more easily\n\nThe packaged guidance is now one consolidated `teams-cli` skill covering authentication, discovery, reading, messaging, and policies. `teams-cli skills install` installs or refreshes it for supported filesystem-based agents and migrates managed skills from version 0.1 automatically.\n\nClaude Desktop users also receive a versioned Cowork skill ZIP that can be uploaded through Cowork's skill settings. Interactive first-time login can offer agent-skill setup before authentication.\n\n### Diagnose local setup problems\n\nThe new `teams-cli doctor` command checks Node.js and browser availability, the selected identity, session health, managed skills, and detected agent environments without changing your configuration or contacting Teams. Use `teams-cli doctor --json` for structured output.\n\n### Try upcoming builds and stay updated\n\nThe CLI now supports stable and canary update channels, plus immutable branch snapshots for targeted testing. `teams-cli version` shows the installed channel, build provenance, release notes, and available updates. Globally installed stable and canary versions can update themselves with `teams-cli version --upgrade`; snapshot builds remain pinned until you explicitly switch channels.\n\n## Upgrade\n\nFor a global npm installation, run:\n\n```console\nteams-cli version --upgrade\n```\n\nYou can also install the release directly:\n\n```console\nnpm install --global @michaelschnyder/teams-cli@latest\n```\n\nIf you created a policy with version 0.1, open `teams-cli policy edit --open` and recreate it using the new people, group-chat, and channel read/post permissions. The previous `messageSend` policy shape is no longer accepted.\n\n> [!WARNING]\n> This project uses unsupported Microsoft Teams private APIs. Microsoft may change or block them without notice. Obtain organizational approval before use.\n",
30
+ "url": "https://github.com/michaelschnyder/teams-cli/releases/tag/v0.2.0"
33
31
  }
34
32
  }
@@ -3,7 +3,7 @@ name: teams-cli
3
3
  description: Use teams-cli safely for Microsoft Teams authentication, discovery, reading, messaging, and policies.
4
4
  license: MIT
5
5
  metadata:
6
- version: "0.2.0-canary.10.1.ge1da9b48"
6
+ version: "0.2.0"
7
7
  author: teams-cli
8
8
  ---
9
9
 
package/docs/releasing.md CHANGED
@@ -37,7 +37,7 @@ Published npm versions are immutable. If a release is defective, fix it in a new
37
37
 
38
38
  ## Canary releases
39
39
 
40
- Merging a pull request into `main` publishes one prerelease to the `canary` npm tag after the resulting main-branch CI run passes on Ubuntu, macOS, and Windows. The publishing workflow consumes that successful CI result instead of repeating the operating-system matrix. A direct commit to `main` does not publish. Stable releases and manually requested snapshots run package verification on Ubuntu before publishing. The workflow uses the package version when it is already greater than npm's latest stable release; otherwise it assumes the next patch. Versions include the workflow run, attempt, and source commit, while the package embeds the pull request notes and build provenance.
40
+ Merging a pull request into `main` publishes one prerelease to the `canary` npm tag after the resulting main-branch CI run passes on Ubuntu, macOS, and Windows. The publishing workflow consumes that successful CI result instead of repeating the operating-system matrix. A direct commit to `main` does not publish. Stable releases run package verification on Ubuntu without repeating the dependency audit that already gates `main`; manually requested snapshots include the audit because their selected branch might not have passed `main` CI. The workflow uses the package version when it is already greater than npm's latest stable release; otherwise it assumes the next patch. Versions include the workflow run, attempt, and source commit, while the package embeds the pull request notes and build provenance.
41
41
 
42
42
  Install or follow this channel with:
43
43
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@michaelschnyder/teams-cli",
3
- "version": "0.2.0-canary.10.1.ge1da9b48",
3
+ "version": "0.2.0",
4
4
  "description": "A safety-conscious CLI for persistent Microsoft Teams sessions",
5
5
  "type": "module",
6
6
  "bin": {
@@ -66,11 +66,11 @@
66
66
  "node": ">=22.20.0"
67
67
  },
68
68
  "teamsCli": {
69
- "channel": "canary",
69
+ "channel": "stable",
70
70
  "releaseSummary": {
71
- "title": "Restore safe CLI self-upgrades",
72
- "summary": "## Summary",
73
- "url": "https://github.com/michaelschnyder/teams-cli/pull/15"
71
+ "title": "Teams CLI v0.2.0",
72
+ "summary": "## Highlights",
73
+ "url": "https://github.com/michaelschnyder/teams-cli/releases/tag/v0.2.0"
74
74
  }
75
75
  }
76
76
  }