@glrs-dev/assume 0.10.2 → 0.10.4

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,42 @@
1
1
  # @glrs-dev/assume
2
2
 
3
+ ## 0.10.4
4
+
5
+ ### Patch Changes
6
+
7
+ - [#273](https://github.com/iceglober/glrs/pull/273) [`a3728ef`](https://github.com/iceglober/glrs/commit/a3728ef1336cec91762e2f1d7cac6a85ddc2a166) Thanks [@iceglober](https://github.com/iceglober)! - fix(assume): stop fabricating the refresh-token lifetime; honest `gsa status`
8
+
9
+ `gsa status` showed "Refresh token: 6d 22h remaining" even right after auto-refresh
10
+ had failed and the SSO session ended — making it look like auto-refresh was broken.
11
+
12
+ Root cause: `refresh_expires_at` was hardcoded to `now + 7 days` and **reset on
13
+ every refresh** (AWS rotates the refresh token each time). AWS SSO never reports
14
+ the refresh token's real lifetime — it's capped by the org's IAM Identity Center
15
+ session limit (often hours), enforced server-side. So the 7-day number was pure
16
+ fiction, and the daemon also hammered refresh every tick near session end.
17
+
18
+ - `refresh()` no longer rolls `refresh_expires_at` forward on rotation; it
19
+ preserves the ceiling set at login.
20
+ - `gsa status` no longer prints a fabricated refresh-token countdown. While the
21
+ session is live it shows `Auto-refresh: on`; once the SSO token is expired
22
+ (auto-refresh couldn't renew it) it shows `SSO session ended — run: gsa login`.
23
+
24
+ Auto-refresh itself was working correctly the whole time — it just can't extend
25
+ past the org's SSO session limit, which is expected AWS behavior.
26
+
27
+ ## 0.10.3
28
+
29
+ ### Patch Changes
30
+
31
+ - [#271](https://github.com/iceglober/glrs/pull/271) [`1853420`](https://github.com/iceglober/glrs/commit/18534203443cd7e7415ae85ce9d87cbc43df1315) Thanks [@iceglober](https://github.com/iceglober)! - docs(assume): lead the quick start with `gsa init`
32
+
33
+ The `gsa --help` quick start (and the README usage block) still told new users to
34
+ run `gsa login` / `gsa use` first — but those commands now refuse until `gsa init`
35
+ completes (init gate). Reordered both to start with `gsa init`, show that
36
+ `aws s3 ls` then works off the default context, and present `gsa use` as the
37
+ per-shell override. Also notes the pre-init allowlist. (docs-site/assume.md
38
+ "How it works" + "Contexts" updated to match.)
39
+
3
40
  ## 0.10.2
4
41
 
5
42
  ### Patch Changes
package/README.md CHANGED
@@ -17,9 +17,9 @@ Or standalone: `npm i -g @glrs-dev/assume` (then `gsa init`).
17
17
  ## Usage
18
18
 
19
19
  ```bash
20
- gsa login aws # authenticate (opens browser)
21
- gsa use aws dev # switch context (fuzzy match)
22
- aws s3 ls # credentials served locally
20
+ gsa init # one-time setup (required first — see Install)
21
+ aws s3 ls # credentials served locally (default context)
22
+ gsa use aws dev # switch this shell to another context (fuzzy match)
23
23
  gsa status # token expiry, daemon health
24
24
  gsa contexts # list available contexts
25
25
  ```
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@glrs-dev/assume",
3
- "version": "0.10.2",
3
+ "version": "0.10.4",
4
4
  "publishConfig": {
5
5
  "access": "public"
6
6
  },
@@ -51,9 +51,9 @@
51
51
  "typescript": "^5"
52
52
  },
53
53
  "optionalDependencies": {
54
- "@glrs-dev/assume-darwin-arm64": "0.10.2",
55
- "@glrs-dev/assume-darwin-x64": "0.10.2",
56
- "@glrs-dev/assume-linux-x64": "0.10.2",
57
- "@glrs-dev/assume-linux-arm64": "0.10.2"
54
+ "@glrs-dev/assume-darwin-arm64": "0.10.4",
55
+ "@glrs-dev/assume-darwin-x64": "0.10.4",
56
+ "@glrs-dev/assume-linux-x64": "0.10.4",
57
+ "@glrs-dev/assume-linux-arm64": "0.10.4"
58
58
  }
59
59
  }