hi all, since the release of `tailwindcss-rails` 3...
# general
b
hi all, since the release of
tailwindcss-rails
3.0.0 this week, solidus’s CI runs for
solidus:install
look like they pass but actually are failing. this is due to one breaking change in
tailwindcss-rails
(and the newly introduced
tailwindcss-ruby
dependency). we think we have resolved the issue, but because the CI step “Run
solidus:install
with `--sample=false --frontend=starter --authentication=devise`” uses the last released version of
solidus_admin
, CI will never pass on our PR to resolve the issue. i think what we need to do is create a new release of
solidus_admin
in order to fix the CI runs, unfortunately. but i don’t have enough context on the
0.2.0...main
diff to know how complex that is. maybe someone on the core team with more context can help here?
👍🏼 1
c
we can also just lock the dependency and release that if we're not in a place where we can cut a release from
main
t
I am all for a new admin release. There have been a lot improvements lately. Will cut it later.
❤️ 1
Thanks for fixing.
One follow up in order to have any effect https://github.com/solidusio/solidus/pull/5880/files