Elias R.

It's difficult. The refactor would always involve using the CommitMessage classes for rendering and since they are rendered differently than the commitMessage template there would always be a functional change....

Then I see two options right now: 1. Wait with this change until communication about commitMessage (and prTitle) is done 2. Live with it breaking if someone uses a template...

Of course. Currently, the commit message is rendered via the template which is "{{{ commitMessagePrefix }}} {{{ someOtherStuff }}}" per default. In comparison, the CommitMessage class **forces** the prefix to...

@freben as far as I can see this should not be breaking as the new LoggerService is a subset of the old Logger, so for the consumer it shouldn't matter...

I'll try it on monday when I'm on my company computer via local linking in our backstage instance.

@kurtaking I just had a look at this and most of the migration is done, but there appears to be some weird behavior between the snackbar and the backstage alerts...

Hey, I haven't started anything yet so go ahead! :)

@kurtaking the latest release now includes my changes and the auth is working! :) It's probably still a good idea to try to understand how this happened.

any news on this?