Locked respect/validation to latest release to avoid composer conflicts. #471
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
MdNadimHossain
requested review from
vincent-gao,
mayurngondhkar and
yeniatencio
mayurngondhkar
approved these changes
Feb 1, 2024
yeniatencio
approved these changes
Feb 1, 2024
There was a problem hiding this comment.
Hi @MdNadimHossain , are we going to update it in tide_search?
…lease-to-avoid-composer-conflicts
@yeniatencio do we need to update the tide_search ? |
MdNadimHossain
deleted the
task/lock-respect/validation-to-latest-release-to-avoid-composer-conflicts
branch
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.
Jira
Problem/Motivation
dev-master has an update for symfony/polyfill-mbstring which creates conflicts with drupal core 10.1.x dependency.
Fix
Lock it to a stable latest release tag to avoid this conflicts.
Related PRs
Screenshots
TODO