Update composer.json to use Shield v1.0.0 #88
Merged
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
datamweb
requested changes
Jan 1, 2024
Co-authored-by: Pooya Parsa <pooya_parsa_dadashi@yahoo.com>
|
@jozefrebjak thanks, I prefer to use the stable version of Shield. |
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.
@datamweb I would like to keep use this package, but we would like to switch to latest stable version of shield, but then dev-develop is not meet. Can we use tagged version of Shield to be required ? Please take a look and propose other solution to this, maybe something more is needed to update. Thanks.