Fredrik Adelöw

That's mostly up to you. We don't have strong opinions on many vs few commits etc. But do try to rebase instead of merging master into your branch, I'd say.

Oh and remember to re-generate your API reports after, too.

Oh sorry - could you make a changeset (`yarn changeset`) on a `patch` level so that this gets shipped as well?

Run the command `yarn changeset` as described above and follow the instructions, and commit the created file with this PR.

Hi! This was discussed a bit elsewhere - yes, this risks happening with anything that results in very large refresh keys. One way forward could be to either prune keys...

That doesn't work in general since it's indexed, right? Db engines in general aren't fond of indexing massive values.

Depends on the database engine. In postgres, you are permitted to create large columns and indices for them, but at runtime if you try to insert a large value in...

note the build errors, you need to run `yarn build:api-reports` and commit that with your pr

It's active in the sense that we still want it! But the maintainers themselves haven't worked on it since our focus is elsewhere. Regarding email / Jira / slack etc....

> Interesting idea. Would this mean that the knip would be part of `backstage-repo-tools` or a script in `scripts` or even `backstage cli`? It might have to, then, yeah -...