Pull Request Overview page broken since 26.3

[sebastiaanspeck]

Describe the bug

Both in the new UI and the old UI, the view is the same.
This is only the case when on the Overview-page of a Pull Request. The branches Overview-page looks fine.

To Reproduce
Steps to reproduce the behavior:

1. Go to a project with a pull request analysis (<URL_TO_SONARQUBE>/dashboard?id=<projeject_key>&pullRequest=<PR_ID>
2. See error

Expected behavior

The same layout as the branches Overview-page:

Screenshots

Software Versions

• SonarQube Version: 26.3.0
• Plugin Version: 26.3.0

Additional context
Add any other context about the problem here.

[manuellazzari-cargoone]

Can confirm the above.

[mc1arke]

Could one of you try the snapshot from #1232 to see if it fixes the issue please?

[sebastiaanspeck]

Could one of you try the snapshot from #1232 to see if it fixes the issue please?

Will do!

[txwhd]

Is there a way to directly build a plugin without using a mirror image？

[mc1arke]

Is there a way to directly build a plugin without using a mirror image？

The plugin and modified front-end can be built locally using the Gradle and Yarn build processes so don't need a container specifically for build. They get attached to each build pipeline (e.g. https://github.com/mc1arke/sonarqube-community-branch-plugin/actions/runs/23888392326#artifacts) if you're just looking to use the artefacts to deploy to a local sonarqube install

[txwhd]

thx！

[bihari-attila-nx]

Hi,
When can we expect the next release?
Thank you!

[mc1arke]

Hi, When can we expect the next release? Thank you!

I was hoping that Sonarsource would cut the next release of Sonarqube this week and I'd include this fix in releasing a version of the plugin to support that. I'll keep an eye out and perform a bugfix release if there's no obvious movement in Sonarqube in the near future

[jackylamhk]

@mc1arke FYI, SonarQube 26.4.0.121862 was just released.

[valdrin-hoti]

For anyone running into layout issues in the PR overview:

As a temporary workaround, you can disable the grid-template-columns rule on the .sw-grid-cols-12 container.

In DevTools:

• Find the element with class sw-grid-cols-12
• Disable grid-template-columns

This restores a usable layout until the underlying issue is fixed.

Obviously not a permanent fix, but helps unblock usage.