ci: Version Packages#787
Merged
Merged
Conversation
AlemTuzlak
approved these changes
Jun 18, 2026
AlemTuzlak
added a commit
that referenced
this pull request
Jun 24, 2026
GitHub releases are created only by the changesets/action step, and that step has not completed cleanly on any release-triggering run since mid-June (last release: @tanstack/ai-react@0.15.5 on 2026-06-15; npm is now at 0.15.12). The "Version Packages" merge runs (#773, #778, #787, #792, #808, #813) passed the test gate and then FAILED at the "Run Changesets" step: CI ran `changeset publish` and npm advanced, but the step died before the tag-push / GitHub-release phase, so no tags (0.15.6-0.15.12 don't exist) and no releases were created. More recent runs (#814, #825) now fail even earlier, at the test gate (test:kiira), so the changesets step is never reached. Either way npm and GitHub drift apart. (The exact in-step error is no longer recoverable - those runs' logs have expired.) Changes: - Split into a `test` gate job and a `release` job (needs: test) so a flaky run blocks BOTH npm and GitHub releases together, never one without the other. - Add workflow_dispatch so a maintainer recovers a blocked release by re-running the workflow (publish is idempotent) instead of intervening by hand. - Add a self-heal step that enforces "published to npm => GitHub release exists": for any package version on npm without a release it creates the tag + release from the CHANGELOG. Runs even when the changesets step fails mid-way and on manual re-runs, so gaps self-heal - directly covering the failure mode above. - Set GITHUB_TOKEN explicitly on the changesets step and tighten permissions (top-level contents:read; write scoped to the release job).
AlemTuzlak
added a commit
that referenced
this pull request
Jun 24, 2026
GitHub releases are created only by the changesets/action step, and that step has not completed cleanly on any release-triggering run since mid-June (last release: @tanstack/ai-react@0.15.5 on 2026-06-15; npm is now at 0.15.12). The "Version Packages" merge runs (#773, #778, #787, #792, #808, #813) passed the test gate and then FAILED at the "Run Changesets" step: CI ran `changeset publish` and npm advanced, but the step died before the tag-push / GitHub-release phase, so no tags (0.15.6-0.15.12 don't exist) and no releases were created. More recent runs (#814, #825) now fail even earlier, at the test gate (test:kiira), so the changesets step is never reached. Either way npm and GitHub drift apart. (The exact in-step error is no longer recoverable - those runs' logs have expired.) Changes: - Split into a `test` gate job and a `release` job (needs: test) so a flaky run blocks BOTH npm and GitHub releases together, never one without the other. - Add workflow_dispatch so a maintainer recovers a blocked release by re-running the workflow (publish is idempotent) instead of intervening by hand. - Add a self-heal step that enforces "published to npm => GitHub release exists": for any package version on npm without a release it creates the tag + release from the CHANGELOG. Runs even when the changesets step fails mid-way and on manual re-runs, so gaps self-heal - directly covering the failure mode above. - Set GITHUB_TOKEN explicitly on the changesets step and tighten permissions (top-level contents:read; write scoped to the release job).
AlemTuzlak
added a commit
that referenced
this pull request
Jun 24, 2026
GitHub releases are created only by the changesets/action step, and that step has not completed cleanly on any release-triggering run since mid-June (last release: @tanstack/ai-react@0.15.5 on 2026-06-15; npm is now at 0.15.12). The "Version Packages" merge runs (#773, #778, #787, #792, #808, #813) passed the test gate and then FAILED at the "Run Changesets" step: CI ran `changeset publish` and npm advanced, but the step died before the tag-push / GitHub-release phase, so no tags (0.15.6-0.15.12 don't exist) and no releases were created. More recent runs (#814, #825) now fail even earlier, at the test gate (test:kiira), so the changesets step is never reached. Either way npm and GitHub drift apart. (The exact in-step error is no longer recoverable - those runs' logs have expired.) Changes: - Split into a `test` gate job and a `release` job (needs: test) so a flaky run blocks BOTH npm and GitHub releases together, never one without the other. - Add a self-heal step that enforces "published to npm => GitHub release exists": for any package version on npm without a release it creates the tag + release from the CHANGELOG. Runs even when the changesets step fails mid-way, so gaps self-heal on the next release run - directly covering the failure mode above. - Set GITHUB_TOKEN explicitly on the changesets step and tighten permissions (top-level contents:read; write scoped to the release job).
AlemTuzlak
added a commit
that referenced
this pull request
Jun 24, 2026
GitHub releases are created only by the changesets/action step, and that step has not completed cleanly on any release-triggering run since mid-June (last release: @tanstack/ai-react@0.15.5 on 2026-06-15; npm is now at 0.15.12). The "Version Packages" merge runs (#773, #778, #787, #792, #808, #813) passed the test gate and then FAILED at the "Run Changesets" step: CI ran `changeset publish` and npm advanced, but the step died before the tag-push / GitHub-release phase, so no tags (0.15.6-0.15.12 don't exist) and no releases were created. More recent runs (#814, #825) now fail even earlier, at the test gate (test:kiira), so the changesets step is never reached. Either way npm and GitHub drift apart. (The exact in-step error is no longer recoverable - those runs' logs have expired.) Changes: - Split into a `test` gate job and a `release` job (needs: test) so a flaky run blocks BOTH npm and GitHub releases together, never one without the other. - Add a self-heal step that enforces "published to npm => GitHub release exists": for any package version on npm without a release it creates the tag + release from the CHANGELOG. Runs even when the changesets step fails mid-way, so gaps self-heal on the next release run - directly covering the failure mode above. - Set GITHUB_TOKEN explicitly on the changesets step and tighten permissions (top-level contents:read; write scoped to the release job).
AlemTuzlak
added a commit
that referenced
this pull request
Jun 24, 2026
…lege GitHub releases are created only by the changesets/action step, and that step has not completed cleanly on any release-triggering run since mid-June (last release: @tanstack/ai-react@0.15.5 on 2026-06-15; npm is now at 0.15.12). The "Version Packages" merge runs (#773, #778, #787, #792, #808, #813) passed the test gate and then FAILED at the "Run Changesets" step: CI ran `changeset publish` and npm advanced, but the step died before the tag-push / GitHub-release phase, so no tags (0.15.6-0.15.12 don't exist) and no releases were created. More recent runs (#814, #825) now fail even earlier, at the test gate (test:kiira). (The exact in-step error is no longer recoverable - those runs' logs have expired.) Changes: - Split into a `test` gate job and a `release` job (needs: test) so a flaky run blocks BOTH npm and GitHub releases together, never one without the other. - Set GITHUB_TOKEN explicitly on the changesets step. - Tighten permissions: top-level contents:read; write scoped to the release job.
AlemTuzlak
added a commit
that referenced
this pull request
Jun 24, 2026
GitHub releases are created only by the changesets/action step, and that step has not completed cleanly on any release-triggering run since mid-June (last release: @tanstack/ai-react@0.15.5 on 2026-06-15; npm is now at 0.15.12). The "Version Packages" merge runs (#773, #778, #787, #792, #808, #813) passed the test gate and then FAILED at the "Run Changesets" step: CI ran `changeset publish` and npm advanced, but the step died before the tag-push / GitHub-release phase, so no tags (0.15.6-0.15.12 don't exist) and no releases were created. More recent runs (#814, #825) now fail even earlier, at the test gate (test:kiira). (The exact in-step error is no longer recoverable - those runs' logs have expired.) Changes: - Split into a `test` gate job and a `release` job (needs: test) so a flaky run blocks BOTH npm and GitHub releases together, never one without the other. - Tighten permissions: top-level contents:read; write scoped to the release job.
AlemTuzlak
added a commit
that referenced
this pull request
Jun 24, 2026
…aps (#829) ci: gate release on a separate test job, least-privilege permissions GitHub releases are created only by the changesets/action step, and that step has not completed cleanly on any release-triggering run since mid-June (last release: @tanstack/ai-react@0.15.5 on 2026-06-15; npm is now at 0.15.12). The "Version Packages" merge runs (#773, #778, #787, #792, #808, #813) passed the test gate and then FAILED at the "Run Changesets" step: CI ran `changeset publish` and npm advanced, but the step died before the tag-push / GitHub-release phase, so no tags (0.15.6-0.15.12 don't exist) and no releases were created. More recent runs (#814, #825) now fail even earlier, at the test gate (test:kiira). (The exact in-step error is no longer recoverable - those runs' logs have expired.) Changes: - Split into a `test` gate job and a `release` job (needs: test) so a flaky run blocks BOTH npm and GitHub releases together, never one without the other. - Tighten permissions: top-level contents:read; write scoped to the release job.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@tanstack/ai-grok@0.12.1
Patch Changes
c55764a]:@tanstack/ai-groq@0.4.7
Patch Changes
c55764a]:@tanstack/ai-openai@0.15.1
Patch Changes
c55764a]:@tanstack/openai-base@0.8.6
Patch Changes
#786
c55764a- fix(openai): emitstrict: falsefor function tools whose JSON Schema is outside OpenAI's strict subsetThe Responses and Chat Completions tool converters forced
strict: trueonevery function tool. When a tool's schema uses keywords OpenAI's strict
Structured Outputs subset doesn't support (
oneOf/allOf/not/$ref/$defs— routinely emitted by MCP servers such as Notion), the API rejectedthe entire request with
400 Invalid schema for function '…', breakingevery run that included such a tool.
These converters now detect schemas outside the strict subset
(
isStrictModeCompatible) and emit those tools withstrict: false— theschema is passed through (only unsupported
formatkeywords are stripped) sothe tool stays callable. Schemas that fit the strict subset keep
strict: trueand the existing structured-output coercion, so well-behaved tools are
unaffected.