Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecate #92

Open
freben opened this issue Sep 12, 2024 · 0 comments
Open

Deprecate #92

freben opened this issue Sep 12, 2024 · 0 comments

Comments

@freben
Copy link

freben commented Sep 12, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant