Update Smarty to 5.8.2 - #36442
Open
eileenmcnaughton wants to merge 1 commit into
Open
Conversation
This is a security hardening update
|
🤖 Thank you for contributing to CiviCRM! ❤️ We will need to test and review this PR. 👷 Introduction for new contributors...
PR commands & links...
|
Contributor
|
There are two security advisories, one is fixed in 5.8.2 and the other in 5.8.4, so I think we need 5.8.4. |
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
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.
Overview
Update Smarty to 5.8.2
This is a security hardening update
Before
5.7.0
After
5.8.4, restriction set to 5.8.2 plus (that version being the earliest one with all security patches)
Technical Details
Per policy we apply all security updates to the rc (regardless of whether it is known to have any application) - we do a security update if shown to be relevant to Civi.
Note that I don't think there is a reason not to have a composer requirement that allows updates within the 5.x series - in this case I think it's why dependabot didn't kick in
Comments