From 000b61b1ecc0d48ca0aaeffee05a90be18a805c1 Mon Sep 17 00:00:00 2001 From: ti777777 Date: Mon, 22 Jan 2024 19:15:52 +0800 Subject: [PATCH 1/5] Remove redundant end tag (#24) --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 0538d51..ad19156 100644 --- a/README.md +++ b/README.md @@ -58,7 +58,7 @@ In addition to using one of the [container sizes](#configuration) provided by de ```html
-
+
From f8d4307afdd3d913c3ddd406334c1a07f427c5b3 Mon Sep 17 00:00:00 2001 From: saibotk Date: Fri, 22 Mar 2024 18:16:49 +0100 Subject: [PATCH 2/5] ci: add provenance to all published packages (#25) This commit adds provenance for all published packages. See the NPM documentation [0]. Provenance will allow people to verify that the packages were actually built on GH Actions and with the content of the corresponding commit. This will help with supply chain security. For this to work, the `id-token` permission was added only where necessary. [0]: https://docs.npmjs.com/generating-provenance-statements --- .github/workflows/release-insiders.yml | 6 +++++- .github/workflows/release.yml | 3 ++- 2 files changed, 7 insertions(+), 2 deletions(-) diff --git a/.github/workflows/release-insiders.yml b/.github/workflows/release-insiders.yml index 4a91bf2..e0ddd7e 100644 --- a/.github/workflows/release-insiders.yml +++ b/.github/workflows/release-insiders.yml @@ -4,6 +4,10 @@ on: push: branches: [main] +permissions: + contents: read + id-token: write + jobs: build: runs-on: ubuntu-latest @@ -45,6 +49,6 @@ jobs: run: npm version 0.0.0-insiders.${{ env.SHA_SHORT }} --force --no-git-tag-version - name: Publish - run: npm publish --tag insiders + run: npm publish --provenance --tag insiders env: NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }} diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 2b133f8..7108a9a 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -6,6 +6,7 @@ on: permissions: contents: read + id-token: write jobs: build: @@ -44,6 +45,6 @@ jobs: echo "RELEASE_CHANNEL=$(npm run release-channel --silent)" >> $GITHUB_ENV - name: Publish - run: npm publish --tag ${{ env.RELEASE_CHANNEL }} + run: npm publish --provenance --tag ${{ env.RELEASE_CHANNEL }} env: NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }} From ef92eba7a7df60659da1ab8dd584346f00efae73 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ra=C3=BAl=20R=20Pearson?= Date: Fri, 27 Dec 2024 05:08:03 +0700 Subject: [PATCH 3/5] Update README.md (#33) All other plugin README's instruct installation as dev dependency, so I assume that's also considered best practice with this one. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index ad19156..310cc99 100644 --- a/README.md +++ b/README.md @@ -7,7 +7,7 @@ A plugin for Tailwind CSS v3.2+ that provides utilities for container queries. Install the plugin from npm: ```sh -npm install @tailwindcss/container-queries +npm install -D @tailwindcss/container-queries ``` Then add the plugin to your `tailwind.config.js` file: From 802c5d86295b6195e9d9634ea5ca36715fc52150 Mon Sep 17 00:00:00 2001 From: Adam Wathan Date: Thu, 13 Feb 2025 06:40:45 -0500 Subject: [PATCH 4/5] Update README.md --- README.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/README.md b/README.md index 310cc99..8b4ab56 100644 --- a/README.md +++ b/README.md @@ -1,3 +1,6 @@ +> [!NOTE] +> Tailwind CSS v4.0+ supports container queries out of the box, so this plugin is only necessary in earlier versions of the framework. + # @tailwindcss/container-queries A plugin for Tailwind CSS v3.2+ that provides utilities for container queries. From 3c3dd3c69944ac48b8cbcb6d537062a0124501bf Mon Sep 17 00:00:00 2001 From: Adam Wathan Date: Thu, 13 Feb 2025 06:42:01 -0500 Subject: [PATCH 5/5] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 8b4ab56..fa38a2b 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,5 @@ > [!NOTE] -> Tailwind CSS v4.0+ supports container queries out of the box, so this plugin is only necessary in earlier versions of the framework. +> As of Tailwind CSS v4.0, container queries are supported in the framework by default and this plugin is no longer required. # @tailwindcss/container-queries