Skip to content

feat: upgrade to tailwind 4#139

Open
jpntex wants to merge 9 commits into
mainfrom
feat/tailwind4
Open

feat: upgrade to tailwind 4#139
jpntex wants to merge 9 commits into
mainfrom
feat/tailwind4

Conversation

@jpntex
Copy link
Copy Markdown
Member

@jpntex jpntex commented May 21, 2026

🔗 Linked issue

❓ Type of change

  • 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • 👌 Enhancement (improving an existing functionality like performance)
  • ✨ New feature (a non-breaking change that adds functionality)
  • 🧹 Chore (updates to the build process or auxiliary tools and libraries)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

Do we need to publish a new version of a package?

  • Add a changeset pnpm changeset and select what semver changes your PR is adding
    • commit and push the generated changeset file

📝 Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.

📚 Description

@jpntex jpntex force-pushed the feat/tailwind4 branch 2 times, most recently from a167846 to 02c0923 Compare May 25, 2026 14:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant