@lark-project/meegle 1.0.15 → 1.0.17

package/CHANGELOG.md

@@ -8,6 +8,18 @@ versioned section on each npm release.
 
 ## [Unreleased]
 
+## [v1.0.17] - 2026-07-20
+
+### Fixed
+
+- Serialized store-backed OAuth refresh across CLI processes, rejected HTTP 200 error envelopes that omit `access_token`, retried requests with the newly persisted token, and guarded terminal-401 cleanup so a stale process can no longer overwrite or delete fresh credentials ([#40](https://github.com/larksuite/meegle-cli/issues/40)).
+
+## [v1.0.16] - 2026-07-07
+
+### Fixed
+
+- The v1.0.15 package metadata and docs were updated, but its bundled binaries still came from v1.0.9.
+
 ## [v1.0.15] - 2026-07-07
 
 ### Added

package/README.md

@@ -776,6 +776,11 @@ JSON output example (`auth status --format json`) on a rejected token:
 {"authenticated": false, "host": "meegle.com", "reason": "token rejected by server"}
 ```
 
+For credentials managed by `meegle auth login`, token refresh is serialized
+across CLI processes that share a profile. Invalid refresh responses are
+rejected without overwriting the previous credentials, and a late 401 from an
+older process cannot clear a token that another process has already refreshed.
+
 ## Configuration
 
 ### Config File

package/README.zh-CN.md

@@ -751,6 +751,10 @@ JSON 输出示例（`auth status --format json`），token 被拒：
 {"authenticated": false, "host": "meegle.com", "reason": "token rejected by server"}
 ```
 
+对于 `meegle auth login` 管理的凭据，共用同一 profile 的多个 CLI 进程会串行执行
+token refresh。无效的刷新响应不会覆盖原凭据，旧进程晚到的 401 也不会清除其他进程
+刚刷新成功的新 token。
+
 ## 配置
 
 ### 配置文件

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lark-project/meegle",
-  "version": "1.0.15",
+  "version": "1.0.17",
   "description": "Agent-First CLI for Meegle (Lark Project)",
   "license": "MIT",
   "homepage": "https://github.com/larksuite/meegle-cli#readme",