Upgrade to new branch for our fork of laravel-scim-server #13573
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
probot-autolabeler
bot
added
backend
dependencies
|
I've run through a full Azure re-provision based based on this exact branch and it completed with no errors. This is good to go. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This changes our
composer.lockfile to take our latest 'zipball' of our fork of the (very fantastic) arietimmerman/laravel-scim-server, which does our SCIM integration.The fixes in there improve some of our SCIM-trace logging, give us Laravel v10 support (without deprecating anything backwards), and give us the ability to take some Azure AD SCIM-client updates that we were unable to read before.
I've done extensive testing on this, but I'm going to go through one more cycle before I declare this 'ready to merge' - but I'm pretty confident right now.