Repository navigation
Conversation
7801123 ("feat: UI/UX refactor with @evoapi/design-system + full i18n pass") moved the build from Tailwind 3.4 to 4.2 through the @tailwindcss/vite plugin and deleted postcss.config.js and tailwind.config.js. Tailwind v4 needs neither: the pipeline lives in vite.config.ts and src/index.css. The Dockerfile was left COPYing both files, so every docker publish workflow has failed at the build stage since 2026-04-17.
This branch has not been deployed
This file contains hidden or 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
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.
Problem
docker buildfails onmain, ondevelop, and on every release tag. The Dockerfile copies two files that no longer exist in the repository:Both
COPYsteps abort the build beforenpm run buildever runs.Cause
Commit 7801123 — "feat: UI/UX refactor with @evoapi/design-system + full i18n pass" (Nickolas Oliveira, 2026-04-17) — migrated the build from Tailwind 3.4.6 to 4.2.2 through the
@tailwindcss/viteplugin:tailwind.config.jspostcss.config.jsvite.config.tsplugins: [react(), tailwindcss()]src/index.css@import "tailwindcss"package.jsontailwindcss^3.4.6→^4.2.2, adds@tailwindcss/viteDockerfileTailwind v4 with the Vite plugin needs neither a PostCSS config nor a JS config — both files were correctly removed. The Dockerfile's two
COPYlines were not.History of the two files:
dff2c82initial commit — added both5d87fe7Linting improvements — editedpostcss.config.jsb364fadHeader & logout confirmation — editedtailwind.config.js7801123— deleted both, left the Dockerfile staleImpact
Broken since 2026-04-17, for ~6 months:
publish_docker_image_latest.yml— push tomain→ Docker Hub:latestpublish_docker_image_homolog.yml— push todeveloppublish_docker_image.yml— tags*.*.*Fix
Remove the two stale
COPYlines. Two deletions, nothing else.Verification
vite.config.tsline 3/7:import tailwindcss from "@tailwindcss/vite"andplugins: [react(), tailwindcss()]src/index.cssline 1:@import "tailwindcss"package.json:"tailwindcss": "^4.2.2","@tailwindcss/vite": "^4.2.2"No PostCSS or JS config is read at build time, so the image builds without them.