Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MS appear to have temporarily pulled Graph SDK 2.7.0 #3783

Closed
salbeck-sit opened this issue Oct 12, 2023 · 6 comments
Closed

MS appear to have temporarily pulled Graph SDK 2.7.0 #3783

salbeck-sit opened this issue Oct 12, 2023 · 6 comments
Labels
Bug Something isn't working Dependencies Pull requests that update a dependency file

Comments

@salbeck-sit
Copy link
Contributor

Description of the issue

Graph 2.7.0 has been pulled due to an error causing missing cmdlets. I assume Dependencies in the latest release will also be amended accordingly

Microsoft 365 DSC Version

1.23.1011.1

Which workloads are affected

other

The DSC configuration

na

Verbose logs showing the problem

na

Environment Information + PowerShell Version

na
@andikrueger
Copy link
Collaborator

@salbeck-sit
Copy link
Contributor Author

Using Find-Module I still see 2.6.1 as the latest verseion

@salbeck-sit
Copy link
Contributor Author

@sdfarquhar
Copy link

I'm seeing the same issue and now stuck with Microsoft365DSC wanting the 2.7 Graph modules but those all being pulled. See example below:

https://www.powershellgallery.com/packages/Microsoft.Graph.Applications/2.7.0

@andikrueger
Copy link
Collaborator

Just check and I'm able to install the latest release with the following command:

Update-M365DSCDependencies -Force
Uninstall-M365DSCOutdatedDepenendencies

Even though the 2.7.0 release is unlisted, it can be installed forcefully.

@andikrueger andikrueger added Bug Something isn't working Dependencies Pull requests that update a dependency file labels Oct 16, 2023
@salbeck-sit
Copy link
Contributor Author

Interesting. I concur. When I use "Find-Module microsoft.graph.applications" (or similar) I get version 2.6.1
But if I use "find-module ... -requiredversion '2.7.0' (similar to what Update-M365DSCDependencies does) then I do in fact get v2.7.0
So it seems that although 2.7.0 has been unlisted, it appears that modules are still present in the gallery after all.
I wonder what the status is on 'relisting' modules...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Dependencies Pull requests that update a dependency file
Projects
None yet
Development

No branches or pull requests

4 participants