Repository navigation
chore(services): rename built-in service manifests - #295
Merged
Merged
Conversation
enkerewpo
force-pushed
the
chore/builtin-service-names
branch
from
October 24, 2026 15:27
ef67d50 to
e449a66
Compare
enkerewpo
force-pushed
the
chore/builtin-service-names
branch
3 times, most recently
from
October 24, 2026 15:51
ce4dcbf to
b22c626
Compare
The services that ship with Robonix are listed in the package catalog under these names, so their manifests carry them, with the tags and maintainers the catalog requires.
enkerewpo
force-pushed
the
chore/builtin-service-names
branch
from
October 24, 2026 16:29
b22c626 to
a242879
Compare
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.
The services that ship with Robonix are getting their own entries in the package catalog (each listed under this repository with its directory), so Robonix Hub can give them a page, list them in search and add them back to a deployment. The catalog checks that a manifest's name matches its entry, so the manifests need catalog-style names:
services/memorycom.robonix.example.memgraph_servicerobonix.service.memgraphservices/memsearchcom.robonix.example.memsearch_servicerobonix.service.memsearchservices/speechcom.robonix.example.speech_servicerobonix.service.speechservices/voiceprintcom.robonix.example.voiceprint_servicerobonix.service.voiceprintservices/verifiers/scene_verifiercom.robonix.service.scene_verifierrobonix.service.scene_verifierservices/verifiers/vlm_verifiercom.robonix.vlm_verifierrobonix.service.vlm_verifierEach manifest also gets the
tagsandmaintainersthe catalog requires, maintainers taken from who wrote each service. Nothing else in the repository refers to the old names; deployments name these services by path, so they are unaffected.