Add changesets and release pipeline (#19)

Author: jschroeter

.changeset/config.json

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

.changeset/shaggy-things-start.md

@@ -0,0 +1,6 @@
+---
+"@knime/kds-components": patch
+"@knime/kds-styles": patch
+---
+
+Improved tokens

.github/workflows/release.yml

@@ -0,0 +1,35 @@
+name: Release
+
+on:
+  push:
+    branches: [master]
+
+concurrency: ${{ github.workflow }}-${{ github.ref }}
+
+jobs:
+  release:
+    name: Release
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+      pull-requests: write
+    steps:
+      - name: Checkout Repo
+        uses: actions/checkout@v4
+      - uses: pnpm/action-setup@v4
+      - name: Install Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version-file: "package.json"
+          cache: "pnpm"
+      - name: Install dependencies
+        run: pnpm install
+
+      - name: Create Release Pull Request or Publish to npm
+        id: changesets
+        uses: changesets/action@v1
+        with:
+          publish: pnpm run publish
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}

README.md

@@ -69,6 +69,21 @@ Here are some of the most important scripts defined in the top-level [`package.j
 - in VS Code, add the [Figma MCP server](https://github.com/mcp/figma/mcp-server-guide) - use the cloud-based server to not require the Figma desktop app
 - then select a component or a design in Figma, copy the URL including the node id and prompt into Agent mode, e.g.: `implement component: {{FigmaUrl}}`
 
+## Maintaining changelogs & publishing to npm
+
+Every PR with changes that should be published must include changeset file(s) out of which the CHANGELOG file of each package will get generated. Use the following command to create such files:
+
+```sh
+pnpm run changeset
+```
+
+Merge those files with the PR to master.
+
+### Publishing to npm
+
+The [`release` GitHub Action](./.github/workflows/release.yml) will automatically create & update a "Version Packages" PR if it detects
+changeset file(s) on master. Once a release should be published to npm, simply do merge this PR.
+
 # Join the Community!
 
 - [KNIME Forum](https://forum.knime.com/)

bitbucket-pipelines.yml

@@ -12,6 +12,7 @@
     "components"
   ],
   "type": "module",
+  "private": true,
   "scripts": {
     "_preBuild": "pnpm run --filter @knime/kds-styles build",
     "build-storybook": "pnpm _preBuild && storybook build",

documentation/package.json

@@ -1,6 +1,4 @@
 {
-  "name": "@knime/kds-root",
-  "version": "0.0.8",
   "description": "Root package for managing the monorepo for the KNIME Design System",
   "license": "GPL 3 and Additional Permissions according to Sec. 7 (SEE the file LICENSE)",
   "author": "KNIME AG, Zurich, Switzerland",
@@ -21,13 +19,17 @@
     "dev": "pnpm run --filter @knime/kds-documentation storybook",
     "test:unit": "vitest",
     "coverage": "vitest run --coverage",
+    "changeset": "pnpm exec changeset",
+    "changeset:version": "pnpm exec changeset version",
+    "changeset:publish": "pnpm exec changeset publish",
+    "publish": "pnpm build && pnpm changeset:publish",
     "audit": "pnpm audit --prod",
-    "publish": "pnpm -r --filter '@knime/kds-styles' --filter '@knime/kds-components' publish --no-git-checks",
     "prepare": "husky",
     "license-check": "license-check -c",
     "postinstall": "run-p license-check build:styles"
   },
   "devDependencies": {
+    "@changesets/cli": "2.29.7",
     "@knime/eslint-config": "9.3.0",
     "@knime/licenses": "1.3.2",
     "@tsconfig/node24": "catalog:",