@nexalink/carecompass-sdk 0.2.0-beta.11 → 0.2.0-beta.12

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 (4) hide show
  1. package/dist/version.js +1 -1
  2. package/package.json +1 -10
  3. package/CHANGELOG.md +0 -37
  4. package/RELEASE.md +0 -65
package/dist/version.js CHANGED
@@ -1,3 +1,3 @@
1
- export const CARECOMPASS_SDK_VERSION = "0.2.0-beta.11"; // x-release-please-version
1
+ export const CARECOMPASS_SDK_VERSION = "0.2.0-beta.12"; // x-release-please-version
2
2
  export const CARECOMPASS_COMPONENT_VERSION = "1.0.0";
3
3
  export const CARECOMPASS_TELEMETRY_CONTRACT_VERSION = "1.0.0";
package/package.json CHANGED
@@ -1,17 +1,10 @@
1
1
  {
2
2
  "name": "@nexalink/carecompass-sdk",
3
- "version": "0.2.0-beta.11",
3
+ "version": "0.2.0-beta.12",
4
4
  "description": "Embeddable CareCompass SDK and CLI for healthcare ecosystem integrations with Nexalink onboarding, BAA coverage, and API keys.",
5
5
  "type": "module",
6
6
  "packageManager": "bun@1.3.9",
7
7
  "homepage": "https://nexalink.care",
8
- "repository": {
9
- "type": "git",
10
- "url": "https://github.com/nexalink-care/carecompass-sdk.git"
11
- },
12
- "bugs": {
13
- "url": "https://github.com/nexalink-care/carecompass-sdk/issues"
14
- },
15
8
  "keywords": [
16
9
  "carecompass",
17
10
  "nexalink",
@@ -46,11 +39,9 @@
46
39
  "files": [
47
40
  "dist/**/*.js",
48
41
  "dist/**/*.d.ts",
49
- "CHANGELOG.md",
50
42
  "README.md",
51
43
  "TELEMETRY.md",
52
44
  "LICENSE",
53
- "RELEASE.md",
54
45
  "SECURITY_AUDIT.md",
55
46
  "RUNTIME_SECURITY_AUDIT.md"
56
47
  ],
package/CHANGELOG.md DELETED
@@ -1,37 +0,0 @@
1
- # Changelog
2
-
3
- All notable changes to `@nexalink/carecompass-sdk` are documented in this file.
4
-
5
- This project uses [release-please](https://github.com/googleapis/release-please) and conventional commits to prepare changelog and version updates.
6
-
7
- ## [0.2.0-beta.11](https://github.com/nexalink-care/carecompass-sdk/compare/v0.1.0-beta.11...v0.2.0-beta.11) (2026-06-07)
8
-
9
-
10
- ### Features
11
-
12
- * baa self-serve ([3ff6d66](https://github.com/nexalink-care/carecompass-sdk/commit/3ff6d662dc83215b85615515eec01c54600fb9ea))
13
- * baa self-serve (CARE-155) ([92c11df](https://github.com/nexalink-care/carecompass-sdk/commit/92c11df5dfc85df195788f5b5aea03112c4c2420))
14
- * cli update ([99ef0e5](https://github.com/nexalink-care/carecompass-sdk/commit/99ef0e52166b519d8982bd67997fae4a0f1a4bb1))
15
- * implement telemetry (CARE-158) ([6337fd7](https://github.com/nexalink-care/carecompass-sdk/commit/6337fd791dc8bbf2192f2b683dbd2d0ef3bbf03a))
16
- * initial commit ([5369c40](https://github.com/nexalink-care/carecompass-sdk/commit/5369c409361be39caaa84db8d3ab1f98f5aec134))
17
- * initial commit ([26ec799](https://github.com/nexalink-care/carecompass-sdk/commit/26ec79928226e98235cd8c42a348a9e070b948c9))
18
- * necessary comments ([127c834](https://github.com/nexalink-care/carecompass-sdk/commit/127c8346bc865c5054b02490c890a53bd03db97a))
19
- * necessary comments ([d7f0d6b](https://github.com/nexalink-care/carecompass-sdk/commit/d7f0d6b7525b9e6282961b8172415e514305bed0))
20
- * security audit ([8115fe2](https://github.com/nexalink-care/carecompass-sdk/commit/8115fe2a75d522f2560ec1ec0f5d9ea1eb1feba4))
21
- * security audit ([0505ae1](https://github.com/nexalink-care/carecompass-sdk/commit/0505ae11937ab15d51b633c782494fe6af468217))
22
- * telemetry ([8f4dff3](https://github.com/nexalink-care/carecompass-sdk/commit/8f4dff3efc80e6e08ad6f0d19b12b7f85688b406))
23
- * telemetry update ([cd15546](https://github.com/nexalink-care/carecompass-sdk/commit/cd15546a756abfa30bf18705d204e9a21d12822f))
24
- * update cli flow ([69c55d5](https://github.com/nexalink-care/carecompass-sdk/commit/69c55d58d55ad64281384254852da468e20214f4))
25
- * updated init flow ([4bd0acf](https://github.com/nexalink-care/carecompass-sdk/commit/4bd0acfd08255b4614fb04b1d5c92b163fb8bcee))
26
-
27
-
28
- ### Bug Fixes
29
-
30
- * whitespace issue ([764c7fc](https://github.com/nexalink-care/carecompass-sdk/commit/764c7fc23de945f4e358c944312c06c3567b0e5e))
31
-
32
- ## [0.1.0-beta.11] - 2026-05-30
33
-
34
- ### Added
35
-
36
- - Initial beta SDK package with React embed, vanilla mount helper, CLI setup flow, config validation, snippet generation, and local diagnostics.
37
- - Supply-chain and runtime security audit documentation for payer deployments.
package/RELEASE.md DELETED
@@ -1,65 +0,0 @@
1
- # CareCompass SDK Release Process
2
-
3
- This package is public, but production use requires Nexalink onboarding, BAA coverage where PHI may be involved, and Nexalink-issued credentials. Treat each package release as a supply-chain event.
4
-
5
- ## Release Authority
6
-
7
- - Only approved Nexalink maintainers may publish `@nexalink/carecompass-sdk`.
8
- - Publish from the canonical GitHub repository: `https://github.com/nexalink-care/carecompass-sdk`.
9
- - Use the pinned package manager in `package.json` and keep `bun.lock` committed.
10
- - Do not publish from a dirty working tree or from a local branch that has not passed review.
11
-
12
- ## Versioning
13
-
14
- - Version and changelog updates are managed by release-please on `main`.
15
- - Use beta versions for pre-production SDKs and avoid reusing a published version.
16
- - Record security-relevant dependency or packaging changes in the release notes.
17
- - Use conventional commit messages so release-please can classify release notes.
18
-
19
- ## Required Validation
20
-
21
- Run the full local release check before publishing:
22
-
23
- ```bash
24
- bun install --frozen-lockfile
25
- bun run release:check
26
- ```
27
-
28
- `release:check` runs lint, tests, build, dependency audit, and a dry-run package assembly. The package dry run uses `bun pm pack --dry-run --ignore-scripts` so package assembly does not execute install lifecycle scripts.
29
-
30
- Before approval, review the dry-run file list and confirm it contains only:
31
-
32
- - `dist/**/*.js`
33
- - `dist/**/*.d.ts`
34
- - `CHANGELOG.md`
35
- - `README.md`
36
- - `TELEMETRY.md`
37
- - `LICENSE`
38
- - `RELEASE.md`
39
- - `SECURITY_AUDIT.md`
40
- - `RUNTIME_SECURITY_AUDIT.md`
41
- - `package.json`
42
-
43
- Do not publish source maps, local credentials, generated payer configs, test fixtures with secret-like values, `.env` files, package-manager caches, or build logs.
44
-
45
- ## Dependency And Lockfile Controls
46
-
47
- - Use `bun install --frozen-lockfile` in CI to verify reproducible installs.
48
- - Run `bun audit` before every release.
49
- - Review `bun outdated` output during routine maintenance and update dev tooling deliberately.
50
- - Do not add install lifecycle scripts unless the security impact is documented and reviewed.
51
- - Do not trust transitive package lifecycle scripts in Bun unless there is a specific approved need.
52
-
53
- ## Provenance, SBOM, And Publishing
54
-
55
- Preferred production publishing should use npm trusted publishing or `npm publish --provenance --access public` from CI after the release check passes. Local publishing is allowed only for emergency releases approved by the package owners.
56
-
57
- Generate an SBOM during CI when the release pipeline supports it, and retain the SBOM, audit output, package dry-run output, and final tarball integrity in release artifacts.
58
-
59
- Release PRs are opened by `.github/workflows/release-please.yml` using the manifest files under `.github/`. Merging the release PR updates `package.json`, `CHANGELOG.md`, and the release manifest, then creates the GitHub release.
60
-
61
- ## Secret Handling
62
-
63
- - Never place Nexalink SDK API keys, payer credentials, SageMaker credentials, AppSync signing roles, or private endpoint URLs in source, docs, tests, generated snippets, package metadata, or release artifacts.
64
- - CLI credentials must stay in the local credentials file or environment variables described in `README.md`.
65
- - Generated browser embed files may include public payer configuration and prompt text. Review generated files before committing them to an integrating application.