Lines Matching refs:deprecation

358 undergo deprecation. The exceptions to this rule are:
446 documentation must state the deprecation status.
449   * A deprecation notice appears in the API documentation.
453   * Might cause a runtime warning with the [`--pending-deprecation`][] flag or
458   * If used with the [`--throw-deprecation`][] flag, will throw a runtime error.
477 warnings, and errors use the identifier when referring to the deprecation. The
478 documentation for the deprecation identifier must always remain in the API
479 documentation. This is true even if the deprecation is no longer in use (for
482 <a id="deprecation-cycle"></a>
495 deprecation lands on the `main` branch.
498 deprecation level of an API.
960 [`--pending-deprecation`]: ../api/cli.md#--pending-deprecation
961 [`--throw-deprecation`]: ../api/cli.md#--throw-deprecation