chore(release): version packages

[saadmoumou]

Summary

• What does this PR change?

Why

• Why is this change needed?

Checklist

• Added/updated tests (if behavior changed)
• npm run lint passes
• npm run typecheck passes
• npm test passes
• npm run build passes
• Added a changeset (npx changeset) if this affects consumers

Notes

• Anything reviewers should pay attention to?

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Copilot]

Pull request overview

This PR performs a Changesets-driven release/versioning step for @ciscode/health-kit, moving it from the placeholder version to the initial published version and materializing the generated changelog.

Changes:

• Bump @ciscode/health-kit version from 0.0.0 to 0.1.0.
• Add CHANGELOG.md entry for 0.1.0 (initial release notes).
• Remove consumed Changesets files after running changeset version.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
package.json	Updates the package version to 0.1.0 for the release.
CHANGELOG.md	Adds the generated changelog for the 0.1.0 initial release.
.changeset/thick-maps-raise.md	Removes an old/consumed changeset entry.
.changeset/health-kit-v0-1-0.md	Removes the consumed changeset used to generate 0.1.0 changelog/version bump.

[Copilot]

The changelog renders the default value with escaped quotes (\"health\"). In Markdown this will display the backslashes; update it to use normal quotes (e.g., "health" without escaping) so the rendered CHANGELOG matches the intended text.

[Copilot]

### Features and the following bullets are indented relative to the rest of the file. Depending on the Markdown renderer this can be interpreted as part of the preceding list item or as a nested block, which makes the CHANGELOG harder to read. Consider making ### Features a normal top-level heading (no leading spaces) and aligning the feature bullets accordingly.

Suggested change

	### Features
	- `HealthKitModule.register()` and `registerAsync()` — dynamic NestJS module with configurable liveness and readiness probes
	- Built-in `PostgresHealthIndicator` (`SELECT 1`), `RedisHealthIndicator` (`PING`), `HttpHealthIndicator` (GET 2xx check) — all with configurable timeout
	- `createIndicator(name, fn)` — inline factory for simple custom indicators
	- `BaseHealthIndicator` abstract class + `@HealthIndicator('liveness' | 'readiness')` decorator for DI-based custom indicators
	- `GET /{path}/live` and `GET /{path}/ready` endpoints — 200 OK / 503 with `{ status, results[] }` body
	- All indicators run concurrently via `Promise.allSettled`
	- `path` option defaults to `"health"`
	### Features
	- `HealthKitModule.register()` and `registerAsync()` — dynamic NestJS module with configurable liveness and readiness probes
	- Built-in `PostgresHealthIndicator` (`SELECT 1`), `RedisHealthIndicator` (`PING`), `HttpHealthIndicator` (GET 2xx check) — all with configurable timeout
	- `createIndicator(name, fn)` — inline factory for simple custom indicators
	- `BaseHealthIndicator` abstract class + `@HealthIndicator('liveness' | 'readiness')` decorator for DI-based custom indicators
	- `GET /{path}/live` and `GET /{path}/ready` endpoints — 200 OK / 503 with `{ status, results[] }` body
	- All indicators run concurrently via `Promise.allSettled`
	- `path` option defaults to `"health"`