thefrontside / playhouse

Frontside's Backstage Portal
https://backstage.frontside.services/
25 stars 13 forks source link

Deprecate humanitec plugins because hey have their own repo now #404

Closed taras closed 5 months ago

taras commented 5 months ago

Motivation

Humanitec folks are maintaining their plugins in https://github.com/humanitec/humanitec-backstage-plugins we can deprecate these now.

Approach

Added deprecate messages to each package in package.json

changeset-bot[bot] commented 5 months ago

⚠️ No Changeset found

Latest commit: 8ebd58c779c141c52b21ad11046447fe3ce18a50

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

frontsidejack commented 5 months ago
The following preview packages were published: Name Version Install Command
br><pre><code>@frontside/backstage-plugin-humanitec-common</code
0.3.14-tm-deprecate-humanitec-plugins.0

yarn add @frontside/backstage-plugin-humanitec-common@tm-deprecate-humanitec-plugins
br><pre><code>@frontside/backstage-plugin-humanitec</code
0.3.16-tm-deprecate-humanitec-plugins.0

yarn add @frontside/backstage-plugin-humanitec@tm-deprecate-humanitec-plugins
br><pre><code>@frontside/backstage-plugin-humanitec-backend</code
0.3.18-tm-deprecate-humanitec-plugins.0

yarn add @frontside/backstage-plugin-humanitec-backend@tm-deprecate-humanitec-plugins

Generated by @thefrontside/actions Frontside

johanneswuerbach commented 5 months ago

I don’t see this field in https://docs.npmjs.com/cli/v10/configuring-npm/package-json , could you point me to some documentation around this?

Specifics of npm's package.json handling
taras commented 5 months ago

It's part of our publish actions. The action will automatically call npm deprecate when it encounters this this property in package.json