Fix ARM64 APK workflow failure by restoring Tailwind/PostCSS compatibility
User description
The ARM64 APK GitHub Actions run failed during next build because Tailwind v4 was resolved while the repo still uses a Tailwind v3-style PostCSS integration. This PR aligns dependency resolution with the existing CSS/Tailwind configuration so CI build execution is consistent again.
-
Root cause
tailwindcss@4.xwas incompatible with the current PostCSS setup (tailwindcssplugin usage) and existing utility application patterns insrc/app/globals.css.
-
Dependency alignment
- Pinned Tailwind to the v3 line in
package.json:tailwindcss: ^3.4.17
- Updated
package-lock.jsonto enforce the same graph in CI.
- Pinned Tailwind to the v3 line in
-
Behavioral impact
- No feature or UI logic changes.
- Build pipeline now uses a compatible Tailwind/PostCSS toolchain.
// package.json (devDependencies)
{
"tailwindcss": "^3.4.17"
}
Summary by cubic
Fixes the ARM64 APK GitHub Actions workflow failing during next build by pinning Tailwind to v3.
Tailwind v4 was being resolved but is incompatible with the repo's Tailwind v3-style PostCSS integration in src/app/globals.css. This pins tailwindcss to ^3.4.17 in package.json and updates package-lock.json so CI resolves the Tailwind v3 dependency tree (tailwindcss 3.4.19, postcss-load-config, and jiti). No feature or UI behavior changes.
PR Type
Bug fix
Description
-
Downgrade Tailwind CSS to version 3.
-
Resolve PostCSS build failures in CI.
Diagram Walkthrough
flowchart LR
pkg["package.json"] -- "Pin tailwindcss to ^3.4.17" --> lock["package-lock.json"]
lock -- "Ensures compatible build" --> build["CI Next.js Build"]
File Walkthrough
| Relevant files | |||||
|---|---|---|---|---|---|
| Dependencies |
|