Important: This task should only be performed after we are fully out of the maintenance window for the last release of RHDH that uses dependencies from Janus IDP.  Deprecating plugins too early may cause RHDH builds and end users to receive noisy warnings about deprecated packages.

Once migration is complete, we should deprecate all migrated plugins on npm.

Follow the npm documentation on deprecating packages to ensure the process is handled correctly. This involves:

• Accessing the Janus NPM token for authentication.

• Running the npm deprecate command with an appropriate message for each plugin, either:

• • Directing users to the new plugin location, or

• • Indicating that the plugin has been deprecated and will not be replaced.

For implementation reference, see Backstage community script for deprecating archived plugins.

Acceptance Criteria:

• All migrated Janus plugins are correctly deprecated on NPM.

• Each deprecation message clearly communicates whether the plugin has a replacement or is permanently deprecated.

• Any documentation or automation related to plugin maintenance is updated to reflect this process.