[Internal] Deprecate -preview packages already published as stable

[marcosmoura]

Currently, there is no way to deprecate the preview packages that were already promoted to stable. This issue here compiles the list of packages that need to be deprecated once we have an automated way.

The current list of packages that needs a deprecation notice includes:

packages/react-components/react-breadcrumb-preview
packages/react-components/react-infolabel-preview
packages/react-components/react-message-bar-preview
packages/react-components/react-tags-preview
packages/react-components/react-timepicker-compat-preview

Related to https://github.com/microsoft/fluentui/issues/28471

[Hotell]

Suggested Implementation:

1. manual trigger: create new pipeline that will be able to deprecate packages provided via env variable on ADO

• variable should follow npm deprecate arguments https://docs.npmjs.com/cli/v10/commands/npm-deprecate

2. automated trigger during v9 release

when package goes from preview to stable package, all -preview package version should be deprecated.

How can we determine that packages is being released from preview as stable:

couple of metadata we can leverage.

when user executed prepare-initial-release generator:

• it created 2 change files with following info:
  • for package: yarn change --message 'feat: release stable' --type minor --package @proj/react-one
  • for react-components package suite: yarn change --message 'feat: add @proj/react-one to suite' --type minor --package @proj/react-components
• it changed version of package: from 0.x.x to "version": "9.0.0-alpha.0",
• it renamed the package ( stripping -preview ) suffix from it's name