Updating to Webform 6.3.0 on D10 Produces 'Webform Bootstrap' Errors

Sorry to re-open this, but installing the new webform_bootstrap module (1.0.3) first did not work. I should also note that the theme this site is using -- DXPR -- is based on Bootstrap 5. As such, I do have the latest version of Bootstrap 5 installed on this site.

And based on the release notes at https://www.drupal.org/project/webform/releases/6.3.0, I thought that installing webform_bootstrap first and then upgrading webform to 6.3.0 would work perfectly.

Instead, after upgrading to webform 6.3.0, I then went to /update.php and was greeted with this message:

Requirements problem
Status Details
Errors found
Webform Bootstrap
Bootstrap 3.x missing.
Bootstrap 3.x. must be enabled to install the Webform Bootstrap module.
Checked
Web server
Apache
PHP
8.3.31
PHP extensions
Enabled
Database support
Enabled
Database system
MariaDB
Database system version
10.3.39-MariaDB-log-cll-lve
Database support for JSON
Available
Is required in Drupal 10.0.
PHP memory limit
4096M
File system
Writable (public download method)
Unicode library
PHP Mbstring Extension
Minimum schema version
The installed schema version meets the minimum.
Schema version: 10600
Check the messages and try again.

Interestingly, the messages that "Bootstrap 3.x missing." and "Bootstrap 3.x. must be enabled to install the Webform Bootstrap module." did remind me that after installing webform_bootstrap I went to /extend and saw that it was *already* checked as being enabled. So then I went to /admin/reports/updates and saw that webform_bootstrap 1.0.3 was indeed appearing there as installed and active. So I figured it was okay to proceed with installing webform 6.3.0.

So perhaps there is something in here that is getting confused. All I know is that I followed the instructions as given, and believe I'm doing everything correctly, and yet the upgrade path from webform 6.2.10 to 6.3.0 is still giving me problems.

Thanks for the latest release notes update - I think it's closer to making sense to me... However, I'm not sure how to interpret "If you use webform_bootstrap ...". For example, at /admin/reports/updates I see the following:

Webform 6.2.10
Recommended version: 6.3.0 (2026-Jul-07)
Includes: Webform, Webform Bootstrap, Webform Node, Webform Templates, Webform UI

So there it says "Webform Bootstrap" is included, and then I check /admin/modules to see if it's enabled. And here I see:

Webform Bootstrap
Helps support Webform to Bootstrap integration.
Machine name: webform_bootstrap
Version: 6.2.10
Requires: WebformFieldFilterUserSystem

Note that here "Webform Bootstrap" is checked, which I take to be enabled and therefore makes me think that I *am* using it.

So given all this, the latest release notes give me the impression that I am using Webform Bootstrap (whether aware of it or not) and therefore should proceed with installing /project/webform_bootstrap like I did in my previous post....

But since I know that doesn't work, then I'm still not sure what I'm supposed to do to upgrade Webform from 6.2.10 to 6.3.0. The only other option from the release notes is to install /project/webform_deprecated and then try upgrading to Webform 6.3.0 ...

But all things considered, I'm not sure if that's correct either and so am going to hold off on doing anything until the next steps to upgrade /project/webform for this website are more clear.

Hello, a quick follow-up that I just ran the command composer show drupal/webform_bootstrap, and that outputted:

In ShowCommand.php line 300:

Package "drupal/webform_bootstrap" not found, try using --available (-a) to show all available packages.

So it does seem there is a discrepancy here where the composer command shows webform_bootstrap is not installed, while at /admin/modules webform_bootstrap is checked in such a way that it can't be unchecked. That is, webform_bootstrap appears to be required by another module and therefore can't be uninstalled - at least not using the UI.

I hope some of this may help, but since I"m not a programmer and since Webform 6.2.10 seems to be working fine anyway, I probably will just disregard this update. Perhaps someday someone will figure out how it can be updated in this scenario - which is really nothing special or out of the ordinary and therefore I'd think others sites will have (or are having) this same issue.