chore(deps): update dependency postcss-preset-env to v8 #3000
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/postcss-preset-env-8.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
7.8.3
->8.0.1
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.
Hi renovate!
Thank you for creating a PR!
I've deployed the changes of this PR on a preview environment under this URL: https://3000-renovate-postcss-preset-env-8-x--vikunja-frontend-preview.netlify.app
You can use this url to view the changes live and test them out.
You will need to manually connect this to an api running somehwere. The easiest to use is https://try.vikunja.io/.
Have a nice day!
This needs some addtitional changes
We need to adjust the settings.
8260a951ee
to3c7719de9f
3c7719de9f
to75d3110c63
75d3110c63
to133e5ab57b
133e5ab57b
to72f24936b7
72f24936b7
to23111ffb87
23111ffb87
to6678295e45
6678295e45
to17ccce42ed
17ccce42ed
to2b53702a76
2b53702a76
to498f392938
498f392938
tocb4c290c7b
This is not an approve.
Just trying to stop renovate.
Renovate will rebase the PR when it becomes conflicted. Not sure if an approval will change that.
cb4c290c7b
to9b83e66aef
9b83e66aef
tofc7c3311f8
fc7c3311f8
toa6f110eedd
a6f110eedd
to5a18c573c8
5a18c573c8
to901fcc3ab6
901fcc3ab6
to928ace3bb0
928ace3bb0
to7a4f63c212
7a4f63c212
to3aa5dc9575
3aa5dc9575
toceaa49ad13
ceaa49ad13
tob6fea0f951
b6fea0f951
to9a2d7bf276
9a2d7bf276
to9fed833db7
9fed833db7
to56fc05c0f6
56fc05c0f6
toe0080d423d
e0080d423d
to4e94709cae
4e94709cae
toc7e275f0db
c7e275f0db
tod260d9527a
d260d9527a
to07934824ff
07934824ff
tob2e29306ce
b2e29306ce
tof02c9420c3
@dpschen what settings do we need to change?
f02c9420c3
to660ddd01df
At least going through their changelog / migration.
I read somewhere that client side js is disabled by default now for the polyfills. Might be that we rely on one of them.
There could also be plugins that we use and that are not part of the bundle any more.
I did a build of the main branch and one on this branch and diffed the css output, these are different:
diff dist/assets/BaseButton-4f62cd82.css dist-main/assets/BaseButton-0c589ca2.css
diff dist/assets/TaskDetailView-2022c382.css dist-main/assets/TaskDetailView-1545bc35.css
diff dist/assets/background-516f12bd.css dist-main/assets/background-b4a077e1.css
(I don't know how useful that is because it's all minified)
660ddd01df
to5a2a95e34b
5a2a95e34b
to517b807840
517b807840
to1c0e54d3fe
1c0e54d3fe
to445a0dd103
445a0dd103
to690a3d5845
690a3d5845
tof03eab31ac
f03eab31ac
to48f3367f18
48f3367f18
todb16764cd7
db16764cd7
to1c4f165880
1c4f165880
to95e4340f00
I went through the changelog and adjusted our config accordingly. Then I diffed the generated CSS files and went through the changes. These three things stood out:
-webkit-text-decoration: underline;
where they previously only includedtext-decoration: underline
.is now output as
(when the
--delete-width
variable has a default value of20px
)It does the same thing when a fallback was explicitely provided in the css
var()
function. This changes this:now becomes
Notice how the fallback in the old version is a different color than the one specified in the css
var()
function? This snippet is coming from bulma but it looks to me like they tried adding a fallback and messed up the color. There's a few places where it does this.I think none of these changes are blockers or worse than what we currently have, so let's merge this upgrade.