Closed taras closed 5 months ago
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.
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
The following preview packages were published: | Name | Version | Install Command |
---|---|---|---|
br><pre><code>@frontside/backstage-plugin-humanitec-common</code |
|
|
|
br><pre><code>@frontside/backstage-plugin-humanitec</code |
|
|
|
br><pre><code>@frontside/backstage-plugin-humanitec-backend</code |
|
|
Generated by @thefrontside/actions
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
It's part of our publish actions. The action will automatically call npm deprecate when it encounters this this property in package.json
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