Merge branch 'master' into claude/happy-rubin-82DHy

Author: azmy60

.github/workflows/publish.yml

@@ -0,0 +1,40 @@
+name: Tabulator Build & Publish
+
+on:
+  push:
+    tags:
+      - 'v*' # Run on any tag that starts with v (e.g., v1.0.0)
+
+permissions:
+  id-token: write # Required for OIDC
+  contents: write # Required for creating a release
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 22
+
+      # for OIDC
+      - name: Update npm
+        run: npm install -g npm@latest
+
+      - name: Install deps
+        run: npm ci
+
+      - name: Build
+        run: npm run build
+
+      - name: Release
+        uses: softprops/action-gh-release@v3
+        with:
+          generate_release_notes: true
+
+      - name: Publish Package
+        run: npm publish --access public

.gitignore

@@ -10,3 +10,5 @@ npm-debug.log
 /playwright-report/
 /blob-report/
 /playwright/.cache/
+
+dist/

CLAUDE.md

@@ -0,0 +1,27 @@
+This is a zero-dependency JS grid library.
+
+Never introduce non-dev dependencies.
+
+When fixing bugs:
+1. Try to add a failing test first to validate the bug - unit, integration, or e2e. Unit testing preferred whenever possible.
+2. Use mocks minimally, so we can recreate bug behavior as close to a real environment as possible.
+3. This library is very modular, pay attention to unintended consequences of a change across modules.
+4. When writing a PR for a bug issue - make sure to have the syntax "Fix #bugid" included in the PR description so that GitHub will auto-close the issue.
+5. Add a small comment to tests that fix specific issues with a link to the issue with a 1-sentence note. eg:
+  ```
+   // Fix https://github.com/xyz/abc/issues/1
+   // Date times not formatting correctly
+  ```
+
+
+Testing approach:
+1. Test as much as possible with unit tests
+2. e2e tests can be used for UI bugs, be conservative and careful with these as e2e tests can become flaky.
+3. If you really can't test something, that's fine, just make a note of it.
+4. Minimal mocking
+5. Follow test folder and structure conventions.
+
+Architecture:
+
+Tabulator's core code is fairly small by design, most functionality is added by modules. We should follow this convention.
+Modules can interact with each other, so always consider the effect of a module change on other modules.

bin/make-release.sh

@@ -0,0 +1,109 @@
+#!/bin/bash
+
+set -euo pipefail
+
+# Function to list the 5 most recent remote tags by date
+list_recent_remote_tags() {
+  echo "Fetching the 5 most recent remote tags by date:"
+  git ls-remote --tags origin | \
+    grep -E 'refs/tags/v[0-9]+\.[0-9]+\.[0-9]+(-[a-z]+\.[0-9]+)?$' | \
+    while read -r hash ref; do
+      tag="${ref#refs/tags/}"
+      date=$(git log -1 --format='%ci' "$hash" 2>/dev/null || echo "unknown date")
+      echo "$tag $date"
+    done | sort -k2 -r | head -n 5
+}
+
+# Function to get the next version in sequence
+guess_next_version() {
+  # Get the most recent tag
+  local latest_tag
+  latest_tag=$(git ls-remote --tags origin | \
+    grep -Eo 'v[0-9]+\.[0-9]+\.[0-9]+(-[a-z]+\.[0-9]+)?$' | \
+    sort -V | tail -n 1)
+
+  # Strip 'v' from the tag
+  latest_version="${latest_tag#v}"
+
+  if [[ "$latest_version" =~ ^([0-9]+)\.([0-9]+)\.([0-9]+)(-(alpha|beta)\.([0-9]+))?$ ]]; then
+    major="${BASH_REMATCH[1]}"
+    minor="${BASH_REMATCH[2]}"
+    patch="${BASH_REMATCH[3]}"
+    channel="${BASH_REMATCH[5]:-}"
+    channel_num="${BASH_REMATCH[6]:-}"
+
+    if [[ -n "$channel" ]]; then
+      # Increment the channel number for pre-releases
+      channel_num=$((channel_num + 1))
+      echo "$major.$minor.$patch-$channel.$channel_num"
+    else
+      # Increment the patch version for stable releases
+      patch=$((patch + 1))
+      echo "$major.$minor.$patch"
+    fi
+  else
+    echo "1.0.0" # Default to this if no valid tags exist
+  fi
+}
+
+# Function to validate version format
+validate_version() {
+  if [[ "$1" =~ ^v?([0-9]+\.[0-9]+\.[0-9]+(-[a-z]+\.[0-9]+)?)$ ]]; then
+    echo "${BASH_REMATCH[1]}"
+  else
+    echo "Error: Invalid version format. Expected x.x.x or x.x.x-channel.x"
+    exit 1
+  fi
+}
+
+# Step 1: List recent tags
+list_recent_remote_tags
+
+# Step 2: Prompt user for new version with a default guess
+default_version=$(guess_next_version)
+echo ""
+read -p "Enter the new version (default: $default_version): " INPUT_VERSION
+VERSION="${INPUT_VERSION:-$default_version}"
+
+# Step 3: Validate and clean the version
+VERSION=$(validate_version "$VERSION")
+NEW_TAG="v$VERSION"
+
+# Confirm with the user
+echo ""
+echo "This will:"
+echo "  - Update package.json to version: $VERSION"
+echo "  - Push a new git tag: $NEW_TAG"
+read -p "Do you want to continue? (y/n): " CONFIRM
+
+if [[ "$CONFIRM" != "y" ]]; then
+  echo "Aborted."
+  exit 0
+fi
+
+# Step 4: Update package.json if necessary
+PACKAGE_VERSION=$(jq -r '.version' package.json)
+if [[ "$PACKAGE_VERSION" == "$VERSION" ]]; then
+  echo "package.json is already updated to version $VERSION."
+else
+  echo "Updating package.json..."
+  jq ".version = \"$VERSION\"" package.json > package.temp.json
+  mv package.temp.json package.json
+
+  # Commit changes
+  echo "Committing changes..."
+  git add package.json
+  git commit -m "chore: bump version to $VERSION"
+  git push
+fi
+
+# Step 5: Push tag
+if git tag | grep -q "$NEW_TAG\$"; then
+  echo "Tag $NEW_TAG already exists."
+else
+  echo "Creating and pushing tag $NEW_TAG..."
+  git tag "$NEW_TAG"
+  git push origin "$NEW_TAG"
+fi
+
+echo "Release process completed successfully."