From 5bad99b53f7bcabce1f8341e7472da839f7d4689 Mon Sep 17 00:00:00 2001 From: gimenes Date: Mon, 11 May 2026 11:20:24 -0300 Subject: [PATCH] feat: publish framework-agnostic entrypoints MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Triggers the semantic-release pipeline to ship the unreleased work sitting on main since v5.0.0: - 736b0b0 Framework-agnostic entrypoints: /core, /tanstack, /next, /node (#164) - 014f8d9 / 95d1f03 chore(migrate): align scaffold + skill with CF-native observability PR #164 introduced the /core, /tanstack, /next, and /node import paths, which is a minor-bump feature surface that never got published because none of the merge commits since v5.0.0 used a release-triggering conventional-commit prefix. Also reverts package.json back to 5.0.0 — semantic-release owns the version field via @semantic-release/exec's prepareCmd (npm version --no-git-tag-version), and PR #165's manual bump to 5.1.0 caused the npm publish step to error with "Version not changed" on the next release-worthy push. Net effect when this merges to main: semantic-release sees a feat: commit since v5.0.0 → computes nextRelease v5.1.0 → npm version 5.1.0 succeeds (package.json is 5.0.0) → publishes @decocms/start@5.1.0 to npm → tags v5.1.0 → moves the v5 floating tag forward Co-Authored-By: Claude Opus 4.7 (1M context) --- package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package.json b/package.json index 61f09b8b..3a2f4cd8 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "@decocms/start", - "version": "5.1.0", + "version": "5.0.0", "type": "module", "description": "Deco framework for TanStack Start - CMS bridge, admin protocol, hooks, schema generation", "main": "./dist/index.cjs",