Add changesets configuration to handle versioning and publishing

Author: bidoubiwa

.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/config.json

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

CONTRIBUTING.md

@@ -103,6 +103,10 @@ As minimal requirements, your commit message should:
 
 We don't follow any other convention, but if you want to use one, we recommend [this one](https://chris.beams.io/posts/git-commit/).
 
+### Changesets <!-- omit in TOC -->
+
+We use [changesets](https://github.com/Noviny/changesets) to do versioning. What that means is that you need to add a changeset by running `yarn changeset` which contains what packages should be bumped, their associated semver bump types and some markdown which will be inserted into changelogs.
+
 ### GitHub Pull Requests <!-- omit in TOC -->
 
 Some notes on GitHub PRs:
@@ -113,6 +117,8 @@ Some notes on GitHub PRs:
 - All PRs must be reviewed and approved by at least one maintainer.
 - The PR title should be accurate and descriptive of the changes. The title of the PR will be indeed automatically added to the next [release changelogs](https://github.com/meilisearch/instant-meilisearch/releases/).
 
+
+
 ## Release Process (for the internal team only)
 
 Meilisearch tools follow the [Semantic Versioning Convention](https://semver.org/).

packages/instant-meilisearch/package.json

@@ -23,7 +23,8 @@
     "dev": "rollup -c rollup.config.js --watch",
     "lint": "eslint --ext .js,.ts,.tsx .",
     "lint:fix": "eslint --ext .js,.ts,.tsx",
-    "test:types": "yarn tsc"
+    "test:types": "yarn tsc",
+    "version": "node scripts/update_version.js"
   },
   "main": "./dist/instant-meilisearch.umd.js",
   "module": "./dist/instant-meilisearch.esm.js",

packages/instant-meilisearch/scripts/update_version.js

@@ -0,0 +1,13 @@
+const pkg = require('../package.json')
+const fs = require('fs')
+const path = require('path')
+
+const version = pkg.version
+
+const pckVersion = `export const PACKAGE_VERSION = '${version}'
+`
+
+const p = path.resolve(__dirname, '../src/package-version.ts')
+
+console.log(p)
+fs.writeFileSync(p, pckVersion)

playgrounds/local-react/package.json

@@ -1,6 +1,7 @@
 {
   "name": "@meilisearch/local-react-playground",
   "version": "0.1.0",
+  "private": true,
   "description": "React playground for instant-meilisearch",
   "main": "src/index.jsx",
   "scripts": {

turbo.json

@@ -16,6 +16,7 @@
     "test:types": {
       "dependsOn": ["^build"],
       "outputs": ["dist/**", "build/**"]
-    }
+    },
+    "version": {}
   }
 }