@thinger-io/cli 0.5.0 → 0.5.1

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.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,21 @@
1
1
  # Changelog
2
2
 
3
+ ## [0.5.1] - 2026-10-31
4
+
5
+ ### Changed
6
+
7
+ - `thinger login` offers the browser login (OAuth device flow) first, with
8
+ the _Thinger CLI_ OAuth client that Thinger 7.5.0 and later create on
9
+ every install. On an older server it says the client is missing and
10
+ offers username and password or a token.
11
+
12
+ ### Fixed
13
+
14
+ - From `@thinger-io/cli-core` 0.5.1: `admin host update-settings` is
15
+ described as the merge the server does, and its confirmation shows what
16
+ changes and what a `null` removes.
17
+ - Requires `@thinger-io/cli-core` 0.5.1.
18
+
3
19
  ## [0.5.0] - 2026-10-31
4
20
 
5
21
  Every command follows one grammar, noun first:
package/README.md CHANGED
@@ -27,7 +27,7 @@ Requires Node.js 20 or newer.
27
27
  ## Signing in
28
28
 
29
29
  ```bash
30
- thinger login # interactive: username/password, token or OAuth
30
+ thinger login # interactive: OAuth (browser), username/password or token
31
31
  thinger login --server acme.aws.thinger.io --username alice --token <API token>
32
32
  ```
33
33
 
@@ -35,8 +35,9 @@ thinger login --server acme.aws.thinger.io --username alice --token <API token>
35
35
  _Thinger CLI_ (id `thinger_cli`) on your account and stores it. `thinger
36
36
  logout` revokes it.
37
37
  - **Token** — paste an existing API token; it is validated and stored as is.
38
- - **OAuth** — browser device flow. Needs an OAuth client registered on the
39
- server (`--client-id`); Thinger servers ship none by default yet.
38
+ - **OAuth** — browser device flow, offered first. It uses the _Thinger CLI_
39
+ OAuth client that Thinger 7.5.0 and later create on every install; on an
40
+ older server the login says so and offers the other two ways.
40
41
 
41
42
  The server is a host (`acme.aws.thinger.io`, HTTPS) or a full URL for plain
42
43
  HTTP or custom ports (`http://localhost:8080`). Self-signed certificates are
package/lib/identity.js CHANGED
@@ -19,9 +19,10 @@ export const thingerIdentity = {
19
19
  npmPackage: '@thinger-io/cli',
20
20
  envPrefix: 'THINGER',
21
21
  token: { id: 'thinger_cli', name: 'Thinger CLI' },
22
- // No OAuth client ships with Thinger servers yet: the browser login asks
23
- // for one registered on the instance.
24
- oauth: { clientId: null },
22
+ // "Thinger CLI", the OAuth client Thinger 7.5.0 and later create on
23
+ // every install. Older servers lack it: the login then offers username
24
+ // and password or a token.
25
+ oauth: { clientId: '3b40164d28730e416cbe' },
25
26
  defaultServer: null,
26
27
  mcp: { serverName: 'thinger', toolPrefix: 'thinger' },
27
28
  };
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@thinger-io/cli",
3
- "version": "0.5.0",
3
+ "version": "0.5.1",
4
4
  "description": "CLI for Thinger.io servers — devices, products, buckets, dashboard apps — with an MCP server for AI clients",
5
5
  "main": "bin/thinger.js",
6
6
  "bin": {
@@ -38,7 +38,7 @@
38
38
  "author": "Thinger.io",
39
39
  "license": "MIT",
40
40
  "dependencies": {
41
- "@thinger-io/cli-core": "^0.5.0"
41
+ "@thinger-io/cli-core": "^0.5.1"
42
42
  },
43
43
  "type": "module",
44
44
  "engines": {