Follow the Backstage releases

[ghost]

Hi,

the plugin has not been updated since Oct 6th. This is a problem with Backstage being released weekly, the dependencies are conflicting.

Do you have any plans to release weekly, and keep compatibility with Backstage?

[eric-despain]

The Backstage release timeline and policy can be found here https://backstage.io/docs/overview/versioning-policy

By not following the Backstage cadence, this is causing issues such as #90

[alecjacobs5401]

Bumping this - looks like since last update, there are some pinned core package versions which is causing

[0] ⚠️   Some of the following packages may be outdated or have duplicate installations:
[0]
[0]           @backstage/backend-app-api, @backstage/backend-common, @backstage/backend-plugin-api, @backstage/catalog-model, @backstage/core-components, @backstage/core-plugin-api, @backstage/plugin-catalog-react, @backstage/plugin-permission-common
[0]
[0] ⚠️   This can be resolved using the following command:
[0]
[0]           yarn backstage-cli versions:check --fix

for newer Backstage instances.

Nothing is explicitly broken yet, but still would be nice to have up to date packages given that Backstage is now on v1.11.1

[alecjacobs5401]

@aarlaud bumping this^^

Any insight or plans to update dependencies?

[brianphillips]

I'm also wondering if there's a need to pin to specific patch versions given most other backstage plugins use a semantic version range for their dependencies instead. Of all our backstage plugins, backstage-plugin-snyk is the one that consistently pulls in some really outdated versions (e.g. backstage-plugin-snyk@2.1.0 is pinned to @backstage/core-components@0.12.4 which is 7 months old).