@gojinko/plugin 2.22.1 → 2.23.0

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "jinko",
   "description": "Search flights, book trips, and manage bookings with the Jinko Travel API. Connects to the Jinko MCP server for live flight pricing, trip management, and payment.",
-  "version": "2.22.1",
+  "version": "2.23.0",
   "author": {
     "name": "Jinko",
     "url": "https://gojinko.com"

package/.codex-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "jinko",
   "description": "Search flights, book trips, and manage bookings with the Jinko Travel API. Connects to the Jinko MCP server for live flight pricing, trip management, and payment.",
-  "version": "2.22.1",
+  "version": "2.23.0",
   "author": {
     "name": "Jinko",
     "url": "https://gojinko.com"

package/README.md

@@ -47,10 +47,13 @@ codex plugin install @gojinko/plugin
 
 ## Authentication
 
-The plugin supports two auth methods:
+Authenticate with a tenant **API key** (`jnk_*`) — get one from
+**dashboard.gojinko.com → Developers → API keys**:
 
-- **API Key**: Set `JINKO_API_KEY` environment variable with your `jnk_*` key
-- **OAuth**: If no API key is set, Codex will auto-discover OAuth and prompt you to sign in via browser
+- Set the `JINKO_API_KEY` environment variable with your `jnk_*` key, or
+- Store it via the CLI: `jinko auth login --key jnk_...`
+
+OAuth sign-in is deprecated and no longer supported.
 
 ## MCP server
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gojinko/plugin",
-  "version": "2.22.1",
+  "version": "2.23.0",
   "description": "Jinko Travel plugin for Claude Code and OpenAI Codex — flight search, booking, and trip management via MCP",
   "private": false,
   "license": "MIT",

package/skills/account/SKILL.md

@@ -14,7 +14,7 @@ Account management is handled through the web dashboard — there are no MCP too
 1. **Register** — go to [gojinko.com/dashboard](https://gojinko.com/dashboard) and sign up with your email.
 2. **Create an API key** — in the dashboard, go to API Keys and create a new key. The full key (prefixed `jnk_`) is shown only once — save it immediately.
 3. **Set your key** — configure your environment:
-   - CLI: `jinko auth login` (OAuth) or set `JINKO_API_KEY=jnk_...`
+   - CLI: `jinko auth login --key jnk_...` (or set `JINKO_API_KEY=jnk_...`)
    - API client: pass the key when creating the client
    - MCP: use `Authorization: Bearer jnk_...` header
 
@@ -33,7 +33,10 @@ Account management is handled through the web dashboard — there are no MCP too
 
 ## CLI authentication
 
-The CLI supports two auth methods:
+The CLI authenticates with an **API key** (`jnk_...`):
 
-1. **OAuth** (recommended): `jinko auth login` — opens a browser for WorkOS login, stores token locally
-2. **API key**: set `JINKO_API_KEY=jnk_...` in your environment — simpler for scripts and CI
+- `jinko auth login --key jnk_...` — stores the key in `~/.jinko/config.yaml`
+- `jinko auth login` (no flag) — prompts for the key interactively
+- `export JINKO_API_KEY=jnk_...` — pass it via the environment (scripts and CI)
+
+OAuth sign-in is deprecated and no longer supported.

package/skills/cli/SKILL.md

@@ -10,14 +10,14 @@ Command-line tool for the Jinko Travel platform. Same capabilities as the MCP to
 ## Install + auth
 
 ```bash
-npm install -g @gojinko/cli     # one-time install
-jinko auth login                 # OAuth device flow → browser login
-jinko auth status                # verify
+npm install -g @gojinko/cli          # one-time install
+jinko auth login --key jnk_xxx        # store your API key (from dashboard.gojinko.com → Developers → API keys)
+jinko auth status                     # verify
 ```
 
 Auth alternatives:
-- **API key** (for scripts / CI): `jinko --api-key jnk_xxx <command>` or `export JINKO_API_KEY=jnk_xxx`.
-- **OAuth (human)**: `jinko auth login` opens a browser, stores token in `~/.jinko/config.yaml`. Auto-refresh is built in. `jinko auth logout` to clear.
+- **API key** (recommended): `jinko auth login --key jnk_xxx`, or per-command `jinko --api-key jnk_xxx <command>`, or `export JINKO_API_KEY=jnk_xxx`. `jinko auth login` with no flag prompts for the key interactively and stores it in `~/.jinko/config.yaml`. `jinko auth logout` to clear.
+- **OAuth**: deprecated and no longer supported — use an API key.
 
 ## Environments (prod / sandbox)
 
@@ -146,7 +146,7 @@ jinko refund status --ref JNK-A7B3X9 --last-name Doe
 
 ## Common pitfalls
 
-- **Two auth systems.** CLI OAuth tokens (WorkOS device flow, stored in `~/.jinko/config.yaml`) are NOT interchangeable with MCP OAuth tokens (DCR, different issuer). Don't paste a CLI token into an MCP Bearer header — it will fail with issuer mismatch. Use an API key (`jnk_*`) for cross-surface programmatic access.
+- **Use an API key everywhere.** A tenant API key (`jnk_*`) works across the CLI, the SDK, and MCP Bearer headers — it's the one credential to carry. (OAuth sign-in is deprecated; any legacy WorkOS CLI token in `~/.jinko/config.yaml` is NOT interchangeable with an MCP OAuth token and will fail with an issuer mismatch if pasted into an MCP Bearer header.)
 - **IATA codes**: `--from PAR` uses a CITY code (matches CDG + ORY + BVA); `--from CDG` uses an airport. `flight-search` has `--origin-type city|airport` to disambiguate.
 - **trip_item_token format**: `offer_xxx:fare_yyy` (flight) or `htl_xxx:rate_yyy` (hotel). Always the offer ID + fare/rate ID joined by colon.
 - **Token expiry**: offers cached ~30 min. If `checkout` returns a quote failure, re-run `flight-search`/`hotel-search` to get a fresh token.