Release 0.5.0: version bump#82
Merged
Merged
Conversation
Bump the web UI package version to 0.5.0 as part of the coordinated 0.5.0 release. The @selfpatch/ros2-medkit-client-ts dependency is unchanged (the 0.5.0 client is published separately).
There was a problem hiding this comment.
Pull request overview
Bumps the SPA’s published version metadata to 0.5.0 for the coordinated release, without changing application behavior or dependency pins.
Changes:
- Update
package.jsonpackage version to0.5.0. - Update
package-lock.jsonroot package version entries to0.5.0.
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| package.json | Bumps the package version field to 0.5.0. |
| package-lock.json | Updates the lockfile’s root package version fields to 0.5.0 to stay in sync with package.json. |
Bump the generated TypeScript client to ^0.5.0 and relock. Derive the /logs types from the 0.5.0 generated schema. The 0.5.0 package ships its `generated/` types and now types the /logs endpoints, so the local log interfaces are anchored to `components['schemas']` instead of being hand-rolled to work around an older client. They keep the runtime refinements the UI relies on - a known severity set, an always-present logger context, and required configuration fields - since the schema types those more loosely.
- Data writes use the flattened {type, data} request body; 0.5.0 dropped the
{value: {type, data}} envelope. The publish form already carries the message
type, so this is a shape change only.
- Keep the /faults status=all and /logs severity/context query filters, which
the gateway reads at runtime but the 0.5.0 spec omits, via a self-removing
@ts-expect-error (selfpatch/ros2_medkit#416). They become type-safe once the
client is regenerated from the fixed spec.
- Cast the legacy config-write fallback result through unknown; the 0.5.0 result
type no longer overlaps the legacy shape.
mfaferek93
approved these changes
Jun 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bump the web UI to 0.5.0 as part of the coordinated 0.5.0 release (
package.json+package-lock.json).The
@selfpatch/ros2-medkit-client-tsdependency pin is intentionally unchanged(
^0.1.1): the 0.5.0 client is released separately, and moving the pin to^0.5.0(plus any client-API adaptation) is a follow-up once it is published.
Issue
Part of the coordinated 0.5.0 release (gateway: selfpatch/ros2_medkit#406).
Type
Version-only bump; no code or behaviour change.
Testing
npm run format:check,npm run lint,npm run typecheckcleannpm test -- --run- 414 tests passnpm run buildsucceeds