Migrate from Next.js 14 / React 18 to Next.js 15 / React 19#2323
Migrate from Next.js 14 / React 18 to Next.js 15 / React 19#2323MikeEdgar merged 11 commits intostreamshub:mainfrom
Conversation
5b02b2d to
29f9036
Compare
261783e to
aa5078a
Compare
86a040c to
ee6edfa
Compare
5ca3390 to
b13e8b5
Compare
2ccf4a5 to
1373448
Compare
Signed-off-by: Michael Edgar <medgar@redhat.com> Co-authored-by: hemahg <hhg@redhat.com> Co-Authored-By: dependabot[bot] <support@github.com> Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com> Assisted-by: Claude Code (Sonnet 4.5) <noreply@anthropic.com>
Signed-off-by: Michael Edgar <medgar@redhat.com>
- Fixes to theme icon selection - Additional async function promise conversion - Update timestamp when using in-app refresh button - Fix cluster connection detail drawer - Add missing project column in cluster table when OIDC is enabled - Remove broken auto-refresh on group members tab, topic groups listing, and topic partitions listing Signed-off-by: Michael Edgar <medgar@redhat.com> Assisted-by: Claude Code (Sonnet 4.5) <noreply@anthropic.com>
Signed-off-by: Michael Edgar <medgar@redhat.com>
Signed-off-by: Michael Edgar <medgar@redhat.com>
Signed-off-by: Michael Edgar <medgar@redhat.com>
Signed-off-by: Michael Edgar <medgar@redhat.com>
Signed-off-by: Michael Edgar <medgar@redhat.com>
Signed-off-by: Michael Edgar <medgar@redhat.com>
Signed-off-by: Michael Edgar <medgar@redhat.com>
|
/systemtests run |
jankalinic
left a comment
There was a problem hiding this comment.
Looks great, thanks!
I will run those tests locally as well before giving an approve.
If the playwright assertions work reliably for every / most of the cases, we could refactor the STs to save exec time. Also thanks for the related async update for kubetest4j!
...ests/src/main/java/com/github/streamshub/systemtests/setup/console/ConsoleInstanceSetup.java
Show resolved
Hide resolved
systemtests/src/test/java/com/github/streamshub/systemtests/kafka/KafkaST.java
Show resolved
Hide resolved
| oldOlmChannel: 0.12.x | ||
| newOlmChannel: alpha | ||
| oldOlmChannel: 0.11.x | ||
| newOlmChannel: 0.12.x |
There was a problem hiding this comment.
Shouldn't we always go for the latest => alpha? Or has that channel versioning/naming changed?
There was a problem hiding this comment.
The problem here is that the current build is 0.12.1-snapshot, which is in 0.12.x already. So the initial test for 0.12.0 fails because it automatically updated to 0.12.1-snapshot. I think we need to keep use the version-specific channels here to prevent the current snapshot from getting installed right away.
There was a problem hiding this comment.
So would you recommend using 0.11 -> latest? I'm thinking about how OLM is skipping/upgrading to those versions. I'm fine with version channels, just thinking if there are any cases in which this might cause future issues.
There was a problem hiding this comment.
You mean 0.11.x to alpha instead of 0.11.x to 0.12.x? At the moment that seems like it would work, but there's only one way to find out 😆
Signed-off-by: jkalinic <jkalinic@redhat.com>
|
|
/systemtests run --testcase=KafkaST |
✅ Systemtests run finished - success ✅Test Summary:
Used parameters:
|
jankalinic
left a comment
There was a problem hiding this comment.
Thank you so much for this PR!
|
@alexcreasy this needs to be merged and 0.12.1 released, but please still give your feedback on the changes in case you find anything we can fix in the next patch 🙏 |



use-resize-observerand replace with native implementation