You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the coming months Tailwind CSS will release the new major version v4 which will probably cause a new major version for tailwind-merge as well, leading to a new label context-v3 that will be added to all new issues, PRs and discussions.
What needs to be done
I'd like to update the label.yml GitHub Action workflow so that the label name is configurable in a single place (e.g. as jobs.env.LABEL_NAME of the workflow). The label name should not be updated, I just want to prepare things to make the update simpler once I have to release a new major version of tailwind-merge.
If anyone wants to pick it up, I'm accepting PRs for this and also happy to help if needed. 😊
The text was updated successfully, but these errors were encountered:
Background
This repository has a GitHub Action workflow https://github.com/dcastil/tailwind-merge/blob/v2.5.3/.github/workflows/label.yml (original issue) which adds the label
context-v2
to issues, PRs and discussions. I use this label to categorize issues, etc. into major versions of tailwind-merge so that I know how up to date the data in them is.In the coming months Tailwind CSS will release the new major version v4 which will probably cause a new major version for tailwind-merge as well, leading to a new label
context-v3
that will be added to all new issues, PRs and discussions.What needs to be done
I'd like to update the
label.yml
GitHub Action workflow so that the label name is configurable in a single place (e.g. asjobs.env.LABEL_NAME
of the workflow). The label name should not be updated, I just want to prepare things to make the update simpler once I have to release a new major version of tailwind-merge.If anyone wants to pick it up, I'm accepting PRs for this and also happy to help if needed. 😊
The text was updated successfully, but these errors were encountered: