Andre Wanlin
Andre Wanlin
Though not a direct fix for the underlying issue this may help: https://github.com/backstage/backstage/pull/29368 Ah, missed this was mentioned already. But it will ship in the release this week 👍
Hi @Xantier, can you give this a look, please?
Any updates on this from the CNCF?
Hi @minkimcello, do you happen to have a rough ETA on the new PR to keep moving this forward?
Thanks for the follow up @craigtracey, I'm not coming up with any alternative use cases for this, could you share more on your thinking?
Agree with @Rugvip comments above around improvements to the output. That would make it a lot easier for new adopters to know what to do and for people who are...
Hi @ScottGuymer, this might also be on me. When I reviewed the plugin I suggested using the `DefaultGithubCredentialsProvider` assuming that the APIs would be available like any other within GitHub....
Hi @thenets, I have a [PR](https://github.com/backstage/backstage/pull/27415) to help make this a bit more clear. The [Node Version policy](https://backstage.io/docs/overview/versioning-policy#nodejs-releases) also explains this so we should be linking to that from the...
Hi @thenets, the docs have been updated around this - https://backstage.io/docs/next/getting-started/ - but the build to move them to stable is taking a long time.
Hi @eliassal, it doesn't look like your backend is starting up on port 7007. Are you running this on your workstation directly or via some other service like codespaces with...