@tpsdev-ai/flair-mcp 0.44.13 → 0.45.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.
Files changed (3) hide show
  1. package/dist/env-guard.d.ts +7 -4
  2. package/dist/env-guard.js +7 -4
  3. package/package.json +2 -2
package/dist/env-guard.d.ts CHANGED
@@ -31,10 +31,13 @@ export declare function readEnvOrUnset(name: string, env?: NodeJS.ProcessEnv): s
31
31
  /**
32
32
  * Connection env vars that flair-client's OWN constructor reads straight from
33
33
  * `process.env` as a fallback (see flair-client/src/client.ts:
34
- * `this.url = config.url ?? process.env.FLAIR_URL ?? DEFAULT_URL`). For these,
35
- * skipping the literal only at flair-mcp's call site is NOT enough: flair-client
36
- * re-reads `process.env` and resurrects the `${...}` literal, defeating its own
37
- * default. Such a literal has to be removed from the process env itself.
34
+ * `this.url = config.url ?? readEnvOrUnset("FLAIR_URL") ?? DEFAULT_URL`). For
35
+ * these, skipping the literal only at flair-mcp's call site was NOT enough:
36
+ * flair-client re-read `process.env` and resurrected the `${...}` literal,
37
+ * defeating its own default. As of flair#1254 flair-client's env fallbacks
38
+ * apply this same literal-as-unset guard themselves, so the strip below is
39
+ * defense-in-depth rather than the only line — kept deliberately (an older
40
+ * flair-client on a consumer's disk does not have #1254).
38
41
  *
39
42
  * Only FLAIR_URL qualifies today: it is re-read by flair-client AND flair-mcp
40
43
  * still constructs a client when it is a literal. FLAIR_AGENT_ID is also re-read
package/dist/env-guard.js CHANGED
@@ -38,10 +38,13 @@ export function readEnvOrUnset(name, env = process.env) {
38
38
  /**
39
39
  * Connection env vars that flair-client's OWN constructor reads straight from
40
40
  * `process.env` as a fallback (see flair-client/src/client.ts:
41
- * `this.url = config.url ?? process.env.FLAIR_URL ?? DEFAULT_URL`). For these,
42
- * skipping the literal only at flair-mcp's call site is NOT enough: flair-client
43
- * re-reads `process.env` and resurrects the `${...}` literal, defeating its own
44
- * default. Such a literal has to be removed from the process env itself.
41
+ * `this.url = config.url ?? readEnvOrUnset("FLAIR_URL") ?? DEFAULT_URL`). For
42
+ * these, skipping the literal only at flair-mcp's call site was NOT enough:
43
+ * flair-client re-read `process.env` and resurrected the `${...}` literal,
44
+ * defeating its own default. As of flair#1254 flair-client's env fallbacks
45
+ * apply this same literal-as-unset guard themselves, so the strip below is
46
+ * defense-in-depth rather than the only line — kept deliberately (an older
47
+ * flair-client on a consumer's disk does not have #1254).
45
48
  *
46
49
  * Only FLAIR_URL qualifies today: it is re-read by flair-client AND flair-mcp
47
50
  * still constructs a client when it is a literal. FLAIR_AGENT_ID is also re-read
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@tpsdev-ai/flair-mcp",
3
- "version": "0.44.13",
3
+ "version": "0.45.0",
4
4
  "description": "MCP server for Flair — persistent memory for Claude Code, Cursor, and any MCP client.",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",
@@ -27,7 +27,7 @@
27
27
  },
28
28
  "dependencies": {
29
29
  "@modelcontextprotocol/sdk": "1.27.1",
30
- "@tpsdev-ai/flair-client": "0.44.13",
30
+ "@tpsdev-ai/flair-client": "0.45.0",
31
31
  "zod": "4.3.6"
32
32
  },
33
33
  "license": "Apache-2.0",