chore(composer): update auth-command to v1.3.1 - #1938
Merged
mrrobot47 merged 1 commit intoSep 28, 2026
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Updates
easyengine/auth-commandfrom v1.3.0 to v1.3.1 for the v4.13.0 release. Only that package changes incomposer.lock.auth-command v1.3.1 includes EasyEngine/auth-command#58: the upgrade migration backs up the site auth files, stages the
_wildcard.*htpasswd and ACL files outside the nginx-proxy mounts while the old proxy template is running, and promotes them on the newafter_docker_image_migrationhook (#1936) once the new nginx-proxy image is up, so sibling sites never pick up another site's wildcard auth during an upgrade.