PetalComponents 1.5.0 updates the Update Guide to use Tailwind 3.3.3, but doesn't specify the breaking change in the CHANGELOG file.
Without the breaking change disclaimer or a pinned version protection, folks using tools like dependabot or doing version bump only reading the CHANGELOG will face issue in production.
This just happened at my company:
dependabot created a PR to version 1.5.0 and 1.5.1
the engineer that took the PR didn't find any breaking changes in the CHANGELOG
build to production didn't break, cause tailwind doesn't fail with an exit
deployed app had no CSS at all due the tailwind silent error
Suggestion
Include the breaking change in the CHANGELOG
If possible, pin the tailwind version within petal version
Description
PetalComponents
1.5.0
updates the Update Guide to use Tailwind3.3.3
, but doesn't specify the breaking change in the CHANGELOG file.Without the breaking change disclaimer or a pinned version protection, folks using tools like
dependabot
or doing version bump only reading the CHANGELOG will face issue in production.This just happened at my company:
dependabot
created a PR to version1.5.0
and1.5.1
tailwind
doesn't fail with anexit
tailwind
silent errorSuggestion
tailwind
version withinpetal
versionStacktrace
Log that shows in the
mix assets.deploy
: