-
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(deps): update dependency tailwindcss to v2 - autoclosed #136
Closed
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
renovate
bot
force-pushed
the
renovate/tailwindcss-2.x
branch
2 times, most recently
from
November 29, 2020 23:50
517185a
to
48f9d11
Compare
renovate
bot
force-pushed
the
renovate/tailwindcss-2.x
branch
3 times, most recently
from
December 13, 2020 23:03
d12b6e6
to
8c70264
Compare
renovate
bot
force-pushed
the
renovate/tailwindcss-2.x
branch
2 times, most recently
from
December 27, 2020 23:51
a549cf1
to
0378b1a
Compare
renovate
bot
force-pushed
the
renovate/tailwindcss-2.x
branch
from
January 11, 2021 00:22
0378b1a
to
4375dfd
Compare
renovate
bot
force-pushed
the
renovate/tailwindcss-2.x
branch
2 times, most recently
from
January 24, 2021 23:44
a5c3a72
to
e6fa977
Compare
renovate
bot
force-pushed
the
renovate/tailwindcss-2.x
branch
2 times, most recently
from
February 7, 2021 23:29
f368c26
to
aa597f9
Compare
renovate
bot
force-pushed
the
renovate/tailwindcss-2.x
branch
from
February 24, 2021 19:10
aa597f9
to
139f25d
Compare
renovate
bot
force-pushed
the
renovate/tailwindcss-2.x
branch
from
March 17, 2021 23:18
139f25d
to
f38067f
Compare
renovate
bot
force-pushed
the
renovate/tailwindcss-2.x
branch
from
March 29, 2021 06:56
f38067f
to
a79bdbc
Compare
renovate
bot
force-pushed
the
renovate/tailwindcss-2.x
branch
2 times, most recently
from
April 6, 2021 00:13
81551c5
to
6a9bfd0
Compare
renovate
bot
force-pushed
the
renovate/tailwindcss-2.x
branch
from
April 23, 2021 19:44
6a9bfd0
to
dd5f98d
Compare
renovate
bot
force-pushed
the
renovate/tailwindcss-2.x
branch
from
May 24, 2021 01:47
dd5f98d
to
6ad20d8
Compare
renovate
bot
force-pushed
the
renovate/tailwindcss-2.x
branch
2 times, most recently
from
June 2, 2021 13:59
f9d06e2
to
4e28c31
Compare
renovate
bot
force-pushed
the
renovate/tailwindcss-2.x
branch
4 times, most recently
from
June 18, 2021 15:55
33f5d53
to
d157dbe
Compare
renovate
bot
force-pushed
the
renovate/tailwindcss-2.x
branch
2 times, most recently
from
June 23, 2021 20:14
9410f16
to
d5f529d
Compare
renovate
bot
force-pushed
the
renovate/tailwindcss-2.x
branch
2 times, most recently
from
July 21, 2021 21:14
e60abd6
to
b1bea80
Compare
renovate
bot
force-pushed
the
renovate/tailwindcss-2.x
branch
from
July 23, 2021 12:22
b1bea80
to
212ab87
Compare
renovate
bot
force-pushed
the
renovate/tailwindcss-2.x
branch
2 times, most recently
from
August 30, 2021 13:26
9f8031b
to
acbaebf
Compare
renovate
bot
force-pushed
the
renovate/tailwindcss-2.x
branch
6 times, most recently
from
September 10, 2021 09:39
91d544a
to
da68e9c
Compare
renovate
bot
force-pushed
the
renovate/tailwindcss-2.x
branch
from
September 26, 2021 13:10
da68e9c
to
a8d23a6
Compare
renovate
bot
force-pushed
the
renovate/tailwindcss-2.x
branch
from
October 13, 2021 18:21
a8d23a6
to
e6cf66b
Compare
renovate
bot
force-pushed
the
renovate/tailwindcss-2.x
branch
2 times, most recently
from
October 29, 2021 11:53
3c5e4bb
to
00a4904
Compare
renovate
bot
force-pushed
the
renovate/tailwindcss-2.x
branch
from
November 14, 2021 23:44
00a4904
to
2359cf7
Compare
renovate
bot
changed the title
fix(deps): update dependency tailwindcss to v2
fix(deps): update dependency tailwindcss to v2 - autoclosed
Dec 9, 2021
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.
This PR contains the following updates:
^0.7.4
->^2.2.19
Release Notes
tailwindlabs/tailwindcss
v2.2.19
Compare Source
Fixed
corePlugins
order is consisent in AOT mode (#5928)v2.2.18
Compare Source
Fixed
v2.2.17
Compare Source
Fixed
awaitWriteFinish
setting to avoid occasional stale builds on Windows (#5758)v2.2.16
Compare Source
Fixed
v2.2.15
Compare Source
Fixed
-i
for input file continues to work even though deprecated (#5464)v2.2.14
Compare Source
Fixed
@defaults
in JIT, switch back toclean-css
in case there's any meaningful differences in the output (bf248cb)v2.2.13
Compare Source
Fixed
clean-css
withcssnano
for CDN builds to fix minified builds (75cc3ca)v2.2.12
Compare Source
Fixed
v2.2.11
Compare Source
Fixed
v2.2.10
Compare Source
Fixed
presets: []
in config file (#4903)Added
optimizeUniversalDefaults
flag (a9e160c)v2.2.9
Compare Source
Fixed
@apply
ing utilities that contain variants + the important modifier (#4854)clean-css
to v5.1.4 to fix empty CSS variables in CDN builds (#5338)v2.2.8
Compare Source
Fixed
@apply
(#5249)object-position
utilities (#5245)v2.2.7
Compare Source
Fixed
v2.2.6
Compare Source
Fixed
v2.2.5
Compare Source
Added
self-baseline
utility (I know this is a patch release, no one's going to die relax) (#5000)Changed
JIT: Optimize universal selector usage by inlining only the relevant selectors (#4850))
This provides a very significant performance boost on pages with a huge number of DOM nodes, but there's a chance it could be a breaking change in very rare edge cases we haven't thought of. Please open an issue if anything related to shadows, rings, transforms, filters, or backdrop-filters seems to be behaving differently after upgrading.
Fixed
step-start
andstep-end
in animation utilities (#4795))!*
in templates from ruining everything (#4816))@layer
rules being mistakenly inserted during incremental rebuilds (#4853))[hidden]
works as expected on elements where we override the defaultdisplay
value in Preflight (#4873)backdropOpacity
utilities (#4892)v2.2.4
Compare Source
Fixed
postinstall
script that was preventing people from installing the library (1eacfb9)v2.2.3
Compare Source
Added
npx tailwindcss
(359252c)Fixed
-
is used as a custom separator (#4704)~
when stackingpeer-*
variants (#4757)purge
if provided on the CLI (#4772)resolveConfig
not being importable in Next.js pags (#4725)v2.2.2
Compare Source
Fixed
transform
,filter
, andbackdrop-filter
classes purely to create stacking contexts to minimize the impact of the breaking change (#4700)v2.2.1
Compare Source
Fixed
corePlugins
order is consisent in AOT mode (#5928)v2.2.0
Compare Source
Changed
JIT: Use "tracking" context by default instead of "watching" context for improved reliability with most bundlers (#4514)
Depending on which tooling you use, you may need to explicitly set
TAILWIND_MODE=watch
until your build runner has been updated to support PostCSS'sdir-dependency
message type.Added
background-origin
utilities (#4117)@apply
performance in projects that process many CSS sources (#3178)matchUtilities
API to make it more suitable for third-party use (#4232)raw
syntax inpurge
config (#4272)empty
variant (#3298)modern-normalize
to v1.1 (#4287)theme
function internally, removepostcss-functions
dependency (#4317)screen
function to improve nesting plugin compatibility (#4318)@tailwind variants
directive to replace@tailwind screens
(#4356)dir-dependency
messages inTAILWIND_DISABLE_TOUCH
mode (#4388)before
andafter
pseudo-element variants andcontent
utilities (#4461)transform
andextract
APIs to simplify PurgeCSS/JIT customization (#4469)caret-color
utilities (#4499)lightBlue
tosky
, emit console warning when using deprecated name (#4513)--watch
mode, and more (#4526, 4558)peer-*
variants for styling based on sibling state (#4556)safelist
as a top-level option underpurge
for both JIT and classic engines (#4580)transform
class when using classes likescale-*
,rotate-*
, etc. (#4604)filter
andbackdrop-filter
classes when using classes likecontrast-*
,backdrop-blur-*
, etc. (#4614)blur-none
by default with intent to deprecateblur-0
(#4614)Fixed
calc
andvar
in arbitrary values (#4147)hsl
colors tohsla
when transforming for opacity support instead ofrgba
(#3850)backdropBlur
variants not being generated (#4188)border
utility (#4277)@tailwind
directives (2f15411)group
variants (#4551)Internals
v2.1.4
Compare Source
Fixed
raw
PurgeCSS sources when registering template dependencies (#4542)v2.1.3
Compare Source
Fixed
v2.1.2
Compare Source
Fixed
v2.1.1
Compare Source
Fixed
v2.1.0
Compare Source
Added
mix-blend-mode
andbackground-blend-mode
utilities (#3920)box-decoration-break
utilities (#3911)isolation
utilities (#3914)inline-table
display utility (#3563)list-item
display utility (#3929)filter
andbackdrop-filter
utilities (#3923)v2.0.4
Compare Source
Fixed
var(--bg-opacity)
value asopacityValue
when defining colors as functionsv2.0.3
Compare Source
Fixed
@apply
in Vue components (#3356)theme()
didn't work with colors defined as functions (#2919)dark
variants by default for color opacity utilities (#2975)Added
tailwind.config.cjs
file in Node ESM projects (#3181)cursor-help
by default (#3199)v2.0.2
Compare Source
Fixed
@apply
not working as expected with!important
inside an atrule (#2824)@apply
not working as expected with defined classes (#2832)@apply
when splitting up files (#3032)Added
ring
utility (#2951)v2.0.1
Compare Source
v2.0.0
Compare Source
Added
overflow-ellipsis
andoverflow-clip
utilities (#1289)transform-gpu
to force hardware acceleration on transforms when desired (#1380)inset
plugin (#2630)translate
,inset
, andheight
plugins (#2630, 5259560)@apply
with complex classes, including variants likelg:hover:bg-blue-500
(#2159)2xl
breakpoint at 1536px by default (#2609)group-hover
for color plugins,boxShadow
, andtextDecoration
by default (28985b6, f6923b1)focus
for z-index utilities by default (ae5b3d3)extend
invariants
configuration (#2651)max-w-prose
class by default (#2574)extend
(#2679, #2700)focus-within
for all plugins that havefocus
enabled by default (1a21f072, f6923b1)ring
utilities for creating outline/focus rings using box shadows (#2747, 879f088, e0788ef)5
and95
to opacity scale (#2747)Changed
target
feature and dropped any compatibility with IE 11 (#2571)shadow-outline
,shadow-solid
, andshadow-xs
by default in favor of newring
API (#2747)normalize.css
tomodern-normalize
(#2572)whitespace-no-wrap
towhitespace-nowrap
(#2664)flex-no-wrap
toflex-nowrap
(#2676)clearfix
utility, recommendflow-root
instead (#2766)hover
andfocus
forfontWeight
utilities by default (f6923b1)grid-gap
fallbacks needed for old versions of Safari (5ec45fa)@apply
implementation, slight backwards incompatibilities with previous behavior (#2159)theme
retrieve the expected resolved value when theme value is complex (e13f083c4)truncate
class totextOverflow
core plugin (#2562)scrolling-touch
andscrolling-auto
utilities (#2573)text-6xl
font-size to 3.75rem instead of 4rem (#2619)[hidden]
elements withinspace
anddivide
utilities instead oftemplate
elements (#2642)extend
objects deeply by default (#2679)preserveHtmlElements
option even when using custom PurgeCSS extractor (#2704)tw-
to avoid collisions with end-user custom properties (#2771)v1.9.6
Compare Source
Changed
The
presets
feature had unexpected behavior where a preset config without its ownpresets
key would not extend the default config. (#2662)If you were depending on this unexpected behavior, just add
presets: []
to your own preset to exclude the default configuration.v1.9.5
Compare Source
Fixed
theme
with default line-heights did not resolve correctlyv1.9.4
Compare Source
Fixed
withOptions
API would not trigger rebuilds in watch processesv1.9.3
Compare Source
Fixed
tailwindcss init --full
scaffolded a corrupt config file (https://github.com/tailwindlabs/tailwindcss/issues/2556)Changed
v1.9.2
Compare Source
Fixed
word-wrap
andoverflow-wrap
together, not one or the other sinceword-wrap
is IE-onlyv1.9.1
Compare Source
Fixed
corePlugins
inresolveConfig
to avoid bundling browser-incompatible code (#2548)v1.9.0
Compare Source
Added
presets
config option (#2474)tailwind.config.js
files with availablefuture
flags commented out (#2379)col-span-full
androw-span-full
(#2471)outline
configurable,outline-none
more accessible by default, and addoutline-black
andoutline-white
(#2460)rotate
andskew
values (#2528)xl
,2xl
, and3xl
border radius values (#2529)grid-auto-columns
andgrid-auto-rows
(#2531)defaultLineHeights
andstandardFontWeights
from experimental to futureFixed
word-wrap
instead ofoverflow-wrap
inie11
target mode (#2391)Experimental
2xl
breakpoint (#2468){u}-max-content
and{u}-min-content
utilities to{u}-max
and{u}-min
in experimental extended spacing scale (#2532)v1.8.13
Compare Source
Fixed
v1.8.12
Compare Source
Fixed
v1.8.11
Compare Source
tailwindcss.plugin
work in ESM environments for reasonsv1.8.10
Compare Source
Fixed
dark
experiment from causing third-partydark
variants to inherit stacking behavior (#2382)v1.8.9
Compare Source
Fixed
extendedSpacingScale
experiment (#2358)!important
was stripped from declarations within rules that used@apply
withapplyComplexClasses
(#2376)Changed
future
section to config stubs (#2372, 3090b98)v1.8.8
Compare Source
Fixed
resolveConfig
code path (#2368)v1.8.7
Compare Source
Fixed
class=\"block\"
) weren't extracted properly for purging (#2364)v1.8.6
Compare Source
Fixed
v1.8.5
Compare Source
Fixed
resolveConfig
didn't take into account configs added by feature flags (#2347)v1.8.4
Compare Source
Fixed
@apply
when using theapplyComplexClasses
experiment (#2271)Changed
font-hairline
andfont-thin
tofont-thin
andfont-extralight
behindstandardFontWeights
flag (experimental until v1.9.0) (#2333)v1.8.3
Compare Source
Fixed
font-variant-numeric
utilities would break in combination with most CSS minifier configurations (f3660ce)conservative
purge mode being deprecated once per process (58781b5)v1.8.2
Compare Source
Fixed
plugins
array in your config (#2322)v1.8.1
Compare Source
Fixed
v1.8.0
Compare Source
Added
preserveHtmlElements
option forpurge
(#2283)layers
mode forpurge
(#2288)font-variant-numeric
utilities (#2305)place-items
,place-content
,place-self
,justify-items
, andjustify-self
utilities (#2306)Changed
@layer
at-rules are now grouped with the corresponding@tailwind
at-rule (#2312)Deprecated
conservative
purge mode, deprecated in favor oflayers
v1.7.6
Compare Source
Fixed
@apply
implementation broke when applying a variant class with the important option globally enabledv1.7.5
Compare Source
Changed
v1.7.4
Compare Source
Added
postcss.config.js
fileChanged
@apply
insensitive to whitespace in the newapplyComplexClasses
experimentFixed
applyComplexClasses
experiment didn't behave as expected with rules with multiple selectors, like.foo, .bar { color: red }
v1.7.3
Compare Source
Changed
Fixed
gradientColorStops
plugin was enabledv1.7.2
Compare Source
Added
v1.7.1
Compare Source
Changed
v1.7.0
Compare Source
Added
contents
display utility@apply
with variants and other complex classes (experimental)Deprecated
v1.6.3
Compare Source
Fixed
v1.6.2
Compare Source
Fixed
@keyframes
respecting the important option would break animations in Chromev1.6.1
Compare Source
Fixed
v1.6.0
Compare Source
Added
prefers-reduced-motion
variantsoverscroll-behaviour
utilitiesv1.5.2
Compare Source
Fixed
@apply
with unprefixed class names if you had configured a prefixv1.5.1
Compare Source
Fixed
v1.5.0
Compare Source
Added
variants
supportcontainer
variantsfocus-visible
variantchecked
variantv1.4.6
Compare Source
Changed
v1.4.5
Compare Source
Fixed
divideColor
plugin was using the wrong '' in IE11 target modev1.4.4
Compare Source
Fixed
target: ['browserslist', {...}]
didv1.4.3
Compare Source
Changed
v1.4.2
Compare Source
Fixed
purge: { enabled: false }
was ignored, addpurge: false
shorthandv1.4.1
Compare Source
Changed
v1.4.0
Compare Source
Added
v1.3.5
Compare Source
Removed
fs-extra
dependency to^8.0.0
to preserve Node 8 compatibility until Tailwind 2.0Fixed
space-x-0
didn't work for example)v1.3.4
Compare Source
Fixed
divide-{x/y}-0
utilities didn't work due to missing unit incalc
callv1.3.3
Compare Source
Added
space
,divideWidth
, anddivideColor
utilitiesv1.3.2
Compare Source
responsive
variants forspace
,divideWidth
, anddivideColor
utilitiesv1.3.1
Compare Source
Fixed
space-x
utilities were not being applied correctly due to referencing--space-y-reverse
instead of--space-x-reverse
v1.3.0
Compare Source
Added
space
anddivide
layout utilitiestransition-delay
utilitiesgroup-focus
variantcontainer
classcurrent
to the default color paletteinline-grid
utilityflow-root
display utilityclear-none
utilityv1.2.0
Compare Source
Added
max-w-{screen}
utilitiesmax-w-none
utilityrounded-md
utilityshadow-sm
utilityshadow-xs
utilitystroke-width
utilitiesplugin
andplugin.withOptions
APIsChanged
v1.1.4
Compare Source
Changed
.group
class. I'm sorry 😞Fixed
.group
class was not receiving the user's configured prefix when using theprefix
optionv1.1.3
Compare Source
Fixed
theme
config didn't receive the second utils argumentv1.1.2
Compare Source
Fixed
v1.1.1
Compare Source
Fixed
auto
would fail to make it through the default negative margin configv1.1.0
Compare Source
Added
border-double
utilityFixed
v1.0.6
Compare Source
Fixed
v1.0.5
Compare Source
Added
Changed
!important
directly in Tailwind utility pluginsv1.0.4
Compare Source
Changed
v1.0.3
Compare Source
Changed
@tailwind preflight
instead of@tailwind base
, this is the source of many support requestsv1.0.2
Compare Source
Fixed
@screen
rules weren't bubbled properly when nested in pluginsv1.0.1
[Compare Source](https://github.com/tailwindlabs/tailwindcss/compare/v
Configuration
📅 Schedule: "on the 2nd and 4th day instance on sunday after 9pm" (UTC).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.