Closed (fixed)
Project:
Microsoft 365 Connector
Version:
6.0.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
10 Nov 2025 at 06:07 UTC
Updated:
20 Feb 2026 at 20:44 UTC
Jump to comment: Most recent
When a run in terminal the composer require 'drupal/o365:^6.0@beta', it pulls the beta 1
im working in drupal 10.5.4
1.- run command composer require 'drupal/o365:^6.0@beta' - pulls beta 1
2.- i already remove the module.
3.- clear cache via: drush and composer comands.
4.- i run the command again and still pulling the beta 1 version.
Comments
Comment #2
fabianderijkI tried multiple times on multiple drupal installs and I can't reproduce this. Can you tell a bit more about the different versions of, for instance, Drupal, PHP, etcetera?
Comment #3
liam morlandIs the problem that it is pulling beta 1 instead of a more recent beta? I am seeing this too.
Comment #4
fabianderijkCan you give some more detail? About the Drupal version etc?
Comment #5
liam morlandIf I run
composer require 'drupal/o365:6.0.0-beta5', I get:So, it thinks that
o3656.0.0-beta5 needs to install ao365_ssoproject, but that isn't a separate project. It won't install that because the version doesn't match. For some reason, this doesn't happen with beta1. I don't see any obvious changes since beta1 that would cause this.Comment #6
fabianderijkHmmm, that really weird. I just did a clean install and actually could reproduce this. I will start to debug and let you know!
Comment #7
fabianderijkComment #8
liam morlandIt might be something broken about the drupal.org Composer facade.
Comment #10
fabianderijkOkay, so I added the o365_sso module to the dependencies of the o365 module. This made the composer loophole. The dependency was added in the beta2. This is now reverted, and the beta6 release has been made: https://www.drupal.org/project/o365/releases/6.0.0-beta6
Comment #11
fabianderijk