Thanks! How were you able to figure out it was the webform? That's where we're stuck, the error doesn't say much about where to look.
Getting same error, on a single site out of 50+ sites. No solution yet but will share if we find one.
The piece to pick out of this composer message is the new dependency, a module named "rat" for "RenderArrayTool":
Excerpt: drupal/rat ^1.0.0@rc ... does not match your minimum-stability.
Your composer.json must have minimum-stability set to "stable" so it can't grab the RC version? Try listing both modules:
composer require drupal/inline_entity_form:^2.0@RC drupal/rat:^1.0@RC
UX comment: I just used Project Browser to install my very first module. As a site builder I know what to do next. How would a Drupal newbie find out what to do next? My sample module is GoogleTagManager, so its next step would be go to its config page ( /admin/config/services/google-tag ) and adjust settings. The project page on drupal.org does not provide this info in a very direct way. How could "next steps" be shown in Project Browser? (Guess I'm kind of brainstorming here - how can we help newbies more?)
As a person already familiar with Drupal, I know I can go to the main Extend menu to see options listed below the module, such as Help, Configure, Permissions. Can options like these be visible in Project Browser?
My first thought is that the word "Project", in this initiative's title, would be confusing to me if I were brand new to Drupal. I would be think of my own work as a project, and of things I might add to my Drupal site-in-progress as extensions, or other equivalent terms: add-ons, modules, plugins.
When using the browser, the categories and filters look great, but I did not find one more piece of information I wanted: an indicator of when this a particular project was last updated, or how often it gets updated. Its status might be "Maintained" but the last actual release was two or more years ago - that's not a module I want to look at. Maybe that filter is already there but I'm just not seeing it.
Patch fixes the problem for me. Same problem also seen on Drupal 9.5 when upgrading to the dev version of this module, and the patch fixed it there too.