chore: introduce changesets

.changeset/README.md

@@ -0,0 +1,8 @@
+# Changesets
+
+Hello and welcome! This folder has been automatically generated by `@changesets/cli`, a build tool that works
+with multi-package repos, or single-package repos to help you version and publish your code. You can
+find the full documentation for it [in our repository](https://github.com/changesets/changesets)
+
+We have a quick list of common questions to get you started engaging with this project in
+[our documentation](https://github.com/changesets/changesets/blob/main/docs/common-questions.md)

.changeset/chilled-eels-drum.md

@@ -0,0 +1,5 @@
+---
+"plaiceholder": minor
+---
+
+Fixes a bug in the CSS logic if the source contains transparency (thanks @skirsten!)

.changeset/config.json

@@ -0,0 +1,11 @@
+{
+  "$schema": "https://unpkg.com/@changesets/[email protected]/schema.json",
+  "changelog": "@changesets/cli/changelog",
+  "commit": false,
+  "fixed": [["plaiceholder", "@plaiceholder/*"]],
+  "linked": [],
+  "access": "restricted",
+  "baseBranch": "main",
+  "updateInternalDependencies": "patch",
+  "ignore": ["example-*"]
+}

.changeset/honest-comics-sin.md

@@ -0,0 +1,5 @@
+---
+"@plaiceholder/tailwindcss": patch
+---
+
+Add `sharp` to peerDependencies to avoid installation confusion

CONTRIBUTING.md

@@ -57,6 +57,57 @@ pnpm <script-name> --filter <package-name>
 
 A trade-off with using a personal repo is that permissions are fairly locked-down. In the mean-time releases will be made manually by the project owner.
 
+Releases and versioning are handled by [Changesets](https://pnpm.io/using-changesets).
+
+### Adding Changesets
+
+```sh
+pnpm changeset
+```
+
+### Publishing
+
+1. Switch into the default branch
+
+   ```sh
+   git checkout main
+   ```
+
+2. Bump packages and generate `CHANGELOG.md`s based on the previously specified
+   changesets.
+
+   ```sh
+   pnpm changeset version
+   ```
+
+3. Regenerate the lockfile
+
+   ```sh
+   pnpm install
+   ```
+
+4. Create a commit with the shared version, and push
+
+   ```sh
+   git commit vX.X.X
+   ```
+
+5. Publish all packages to npm
+
+   ```sh
+   pnpm publish -r
+   ```
+
+6. Create a tag with the shared version, then push the commit and tag
+
+   ```sh
+   git tag vX.X.X
+   git push
+   git push origin refs/tags/vX.X.X
+   ```
+
+7. [Create a release](https://github.com/joe-bell/plaiceholder/releases/new), using the newly pushed tag
+
 ## Implementations
 
 So, you want to build an alternative Plaiceholder implementation? Great!
@@ -70,9 +121,9 @@ Please respect that Plaiceholder is just the end result – countless hours of w
 When building your own implementation, you should meet the following requirements:
 
 - Branding
-  - ❌ **Don't** use the "Plaiceholder" name on its own, the logo, tagline or any of the marketing copy from either the [plaiceholder.co](https://plaiceholder.co) domain or [docs](https://plaiceholder.co/docs).  
+  - ❌ **Don't** use the "Plaiceholder" name on its own, the logo, tagline or any of the marketing copy from either the [plaiceholder.co](https://plaiceholder.co) domain or [docs](https://plaiceholder.co/docs).
     The "[Plaiceholder](https://plaiceholder.co)" project is a trading name of "Big Attic OÜ", and therefore should not be confused with affiliation.
-  - ✅ **Do** name your project with the `-plaiceholder` suffix **or** `plaiceholder-` prefix.  
+  - ✅ **Do** name your project with the `-plaiceholder` suffix **or** `plaiceholder-` prefix.
     e.g. your repo or package, could be called `rust-plaiceholder`, your function could be called `rustPlaiceholder` (but **not** `plaiceholder`).
 - Credit
 
@@ -84,7 +135,7 @@ When building your own implementation, you should meet the following requirement
 
        ```md
        <p align="center">
-         An externally-maintained implementation of 
+         An externally-maintained implementation of
          <strong>
             <a href="https://github.com/joe-bell/plaiceholder">
                Plaiceholder
@@ -119,3 +170,7 @@ If you have any questions above the above requirements, please feel free to [rea
 ### Raise a PR
 
 Once you've completed the above, raise a PR to add your implementation to the [Community page](https://plaiceholder.co/docs/community).
+
+```
+
+```

examples/11ty/package.json

@@ -1,7 +1,6 @@
 {
   "private": true,
   "name": "example-with-11ty",
-  "version": "2.3.0",
   "author": "Joe Bell <[email protected]>",
   "license": "Apache-2.0",
   "scripts": {

examples/next/package.json

@@ -1,7 +1,6 @@
 {
   "private": true,
   "name": "example-with-next",
-  "version": "2.3.0",
   "author": "Joe Bell <[email protected]>",
   "license": "Apache-2.0",
   "scripts": {

package.json

@@ -16,6 +16,7 @@
     "prepare": "[[ \"$CI\" -ne \"1\" ]] && [[ \"CI\" != 'true' ]] && pnpm build || echo 'Skipping prepare'"
   },
   "devDependencies": {
+    "@changesets/cli": "2.23.0",
     "@commitlint/cli": "13.1.0",
     "@commitlint/config-conventional": "13.1.0",
     "commitizen": "4.2.4",