Versioning lets software capabilities evolve without forcing every dependent application to change at once. Keep related workflows independently deployable, and keep multiple tool versions available so applications can migrate on their own schedules. section 2.2.3 section 6.2.2
A managed tool registry can make version changes predictable:
- Use semantic versions: major releases mark breaking changes, minor releases add compatible functionality, and patch releases fix bugs. Reject incompatible changes unless they use a major version. section 6.2.2
- Let applications pin version constraints while old and new versions coexist. Deprecate retiring versions, communicate migration guidance, and allow existing applications time to move. section 6.2.2
- Deploy workflows independently so teams can run versions simultaneously and shift traffic gradually without coordinating unrelated releases. section 2.2.3
Listing 6.10 Version-constrained tool discovery
tools = platform.tools.discover(
namespace="healthcare.scheduling.*",
version_constraint="^1.0.0" #A
)
tools = platform.tools.discover(
namespace="healthcare.scheduling.*",
version_constraint=">=1.0.0 <3.0.0" #B
)These discovery calls show two ways to constrain which tool versions an application can use. section 6.2.2



































