npm - higherdata - Versions diffs - 0.3.1 → 0.5.0 - Mend

higherdata 0.3.1 → 0.5.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

package/README.md CHANGED Viewed

@@ -251,3 +251,11 @@ higherdata config set auto-update true
 Explicit `higherdata update` remains available with an opt-out or a server
 minimum-version refusal. Users on 0.3.0 must reinstall once to obtain the update
 command: `npm install --global higherdata@latest`.
+### Credentials and diagnostics
+The CLI stores saved API keys in macOS Keychain, Windows Credential Manager, or Linux Secret Service (for example GNOME Keyring or KWallet). Existing plaintext profiles migrate on first use. Config files retain only a keychain reference. On platforms without a supported keychain, or when a persistent Linux service is absent, the CLI keeps the existing file fallback with mode 0600. A missing native binding, locked store or inaccessible keychain returns an error rather than downgrading credentials. `higherdata logout` removes the active profile's keychain entry. `HIGHERDATA_API_KEY` remains available for CI.
+Server failures print the error code, user-safe message and request id to stderr. JSON and JSONL results stay on stdout. Non-interactive commands also print a one-line newer-version notice on stderr using the existing daily compatibility check.
+When `higherdata tools email.find` returns `status: ambiguous`, select an opaque id from `companyCandidates` and retry with `--company-id`. This choice does not submit verification requests. An exact match to one primary domain is selected automatically when the complete company match set is available.