Conversation
Signed-off-by: Côme Chilliet <[email protected]>
Can someone familiar enough look into https://scssphp.github.io/scssphp/docs/changelog.html and see how big the impact of this bump is? We had 1.4.0 before so it’s a pretty big bump, I’m not sure if the psalm spotted problem is the only one. |
This ports away from using now internal functions from scssphp. Signed-off-by: Carl Schwan <[email protected]>
|
I just did some small grepping and the only misused was the one reported by psaml and I fixed it. Other than that locally everything seems to still works and I followed https://scssphp.github.io/scssphp/docs/#security-considerations to do a bit of hardening |
f9f53e6 to
b706bba
Compare
See https://scssphp.github.io/scssphp/docs/#security-considerations Signed-off-by: Carl Schwan <[email protected]>
30098c8 to
dfb569f
Compare
skjnldsv
left a comment
There was a problem hiding this comment.
We can merge but note that this scsscacher should go away as soon as we have the time to :)
|
@skjnldsv You merged here but it was needed to merge nextcloud/3rdparty#934 first and then rebase here to use the merge commit. |
|
@come-nc make your PR a draft next time 😉 |
But can it get approvals while still being a draft? I wait for CI and approvals on server side before merging 3rdparty side, I thought this was not possible with a draft. |
|
(3rdparty was merged, fixing PR server-side incoming) |
yes |
Signed-off-by: Côme Chilliet [email protected]
nextcloud/3rdparty#934