Fredrik Adelöw

Yeah the DCO check has been really flaky lately. We double check the commits by hand when it happens.

> In order to fix the issue mentioned above, pagination on the catalog’s entities needs to be enforced. Maybe not enforced, but at least better supported. _Enforcing_ is more a...

Yeah the catalog frontend still isn't properly leveraging the backend's pagination capabilities. Essentially it still calls the old APIs that were there before pagination support was added. Therefore, all entities...

I believe this was fixed by #21202 but it needs a prop to be added to the page at this point. See https://backstage.io/docs/releases/v1.21.0#catalog-pagination

Oh sorry there may have been some follow-up actions left at the top still - reopening

Shouldn't be about a missing export if typescript is happy and not complaining about your code, I think. Is this on the new backend system? Did you remember to register...

Hm. These migrations are on a per plugin basis. So you'd want to target a certain plugin on the command line - by ID perhaps? Those are chosen by the...

Ah I missed that you said it would be run in a plugin folder. But in any case the plugin ID is not known from there

Thanks for reporting! Opening this up to contributors who are familiar with how to best solve it.

The [default column width is `auto`](https://github.com/backstage/backstage/blob/1490e585193837baffe97811355cd8c5a443ead0/plugins/catalog/src/components/CatalogTable/columns.tsx#L146) unless I'm mistaken. Any change to that will have significant unwanted impact on other columns, I would assume. I am not sure what to...