Skip to navigation

Deprecations and Removals

View as MarkdownOpen in Claude

The following table lists the features of the NVIDIA NeMo Guardrails library that are deprecated together with the LLMRails engine. A deprecated feature keeps working until a release removes it. The Removal column gives the earliest release that can remove the feature; the release that removes it is not decided yet.

FeatureDeprecated InRemovalReported ThroughReplacementMigration
LLMRails, constructed in your code0.25.0No earlier than 0.27.0LLMRailsRemovalWarningGuardrails, which runs the IORails engineReplace LLMRails with Guardrails
Colang 2.x runtime, including nemoguardrails chat and its debugger commands with a Colang 2.x configuration0.25.0No earlier than 0.27.0LLMRailsRemovalWarning, or a notice from nemoguardrails chatNoneColang Configurations
LLMRails engine0.25.0No earlier than 0.27.0Documentation onlyGuardrails, running the IORails engineConfigurations That Fall Back to LLMRails
Colang 1.0 runtime, including dialog flows (define user, define flow)0.25.0No earlier than 0.27.0Documentation onlyInput and output railsColang Configurations

A feature that is reported through documentation only emits no Python warning when you use it.

When Guardrails runs a configuration on the IORails engine, it also emits a UserWarning for Colang dialog flows, a custom refusal message, and config.py, which that engine ignores. This warning describes what the engine does today and carries no removal date.

For the exact messages and how to silence them, refer to Migrating to 0.25.