Skip to content

Deprecate #92

@freben

Description

@freben

Hey there!

Now that the plugin is completely available and maintained out of the community-plugins repo, I would humbly ask whether it might be time to deprecate this entire repository, to reduce the risk of confusion. One possible way of doing so:

  • Making a README update saying the package is deprecated, and pointing to the URL and package name of its new home
  • Updating the package.json to add a moved pointer to the new package
  • Making one final release to npm to ensure that the newest package version has that information in it
  • Formally marking the package as deprecated using the npm command line tool
  • Reducing the contents of this repo down to just the README and nothing else

Again, this is just a humble suggestion and feel free to do with it as you will. Thanks for all of your work!

Regards,
/your old backstage maintainer friends

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions