Skip to content

chore: version packages - #17076

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main
Open

github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish 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

The changelog information of each package has been omitted from this message, as the content exceeds the size limit.

@objectstack/cli@17.5.0

@objectstack/client@17.5.0

@objectstack/core@17.5.0

@objectstack/driver-memory@17.5.0

@objectstack/driver-sql@17.5.0

@objectstack/driver-sqlite-wasm@17.5.0

@objectstack/driver-turso@17.5.0

@objectstack/formula@17.5.0

@objectstack/lint@17.5.0

@objectstack/mcp@17.5.0

@objectstack/metadata@17.5.0

@objectstack/metadata-core@17.5.0

@objectstack/metadata-protocol@17.5.0

@objectstack/objectql@17.5.0

@objectstack/platform-objects@17.5.0

@objectstack/plugin-approvals@17.5.0

@objectstack/plugin-audit@17.5.0

@objectstack/plugin-auth@17.5.0

@objectstack/plugin-hono-server@17.5.0

@objectstack/plugin-security@17.5.0

@objectstack/rest@17.5.0

@objectstack/runtime@17.5.0

@objectstack/service-analytics@17.5.0

@objectstack/service-automation@17.5.0

@objectstack/service-messaging@17.5.0

@objectstack/service-queue@17.5.0

@objectstack/service-storage@17.5.0

@objectstack/spec@17.5.0

@objectstack/trigger-schedule@17.5.0

@objectstack/types@17.5.0

@objectstack/verify@17.5.0

@objectstack/hono@17.5.0

@objectstack/account@17.5.0

@objectstack/setup@17.5.0

@objectstack/studio@17.5.0

@objectstack/client-react@17.5.0

@objectstack/cloud-connection@17.5.0

@objectstack/connector-mcp@17.5.0

@objectstack/connector-openapi@17.5.0

@objectstack/connector-rest@17.5.0

@objectstack/connector-slack@17.5.0

create-objectstack@17.5.0

@objectstack/driver-mongodb@17.5.0

@objectstack/metadata-fs@17.5.0

@objectstack/observability@17.5.0

@objectstack/embedder-openai@17.5.0

@objectstack/knowledge-memory@17.5.0

@objectstack/knowledge-ragflow@17.5.0

@objectstack/organizations@17.5.0

@objectstack/plugin-dev@17.5.0

@objectstack/plugin-email@17.5.0

@objectstack/plugin-pinyin-search@17.5.0

@objectstack/plugin-reports@17.5.0

@objectstack/plugin-sharing@17.5.0

@objectstack/plugin-webhooks@17.5.0

@objectstack/sdui-parser@17.5.0

@objectstack/service-cache@17.5.0

@objectstack/service-cluster@17.5.0

@objectstack/service-cluster-redis@17.5.0

@objectstack/service-datasource@17.5.0

@objectstack/service-i18n@17.5.0

@objectstack/service-job@17.5.0

@objectstack/service-knowledge@17.5.0

@objectstack/service-package@17.5.0

@objectstack/service-realtime@17.5.0

@objectstack/service-settings@17.5.0

@objectstack/service-sms@17.5.0

@objectstack/trigger-api@17.5.0

@objectstack/trigger-record-change@17.5.0

@objectstack/console@17.5.0

@objectstack/example-crm@4.0.97

@objectstack/example-multi-package@0.0.4

@objectstack/example-showcase@0.3.19

@objectstack/example-todo@4.0.97

@objectstack/example-embed-objectql@0.0.37

@objectstack/dogfood@0.0.45

@objectstack/downstream-contract@0.0.43

@objectstack/http-conformance@0.1.5

@github-actions
github-actions Bot force-pushed the changeset-release/main branch from ca34d66 to 83e005e Compare September 9, 2026 12:15
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 83e005e to 25e2bf8 Compare September 9, 2026 18:13
@github-actions
github-actions Bot force-pushed the changeset-release/main branch 3 times, most recently from d02da01 to f21afd1 Compare September 10, 2026 12:15
@github-actions
github-actions Bot force-pushed the changeset-release/main branch 3 times, most recently from 6ce105b to 7d29fcf Compare September 11, 2026 06:17
@github-actions
github-actions Bot force-pushed the changeset-release/main branch 3 times, most recently from c821cfc to f769cd4 Compare September 12, 2026 00:25
@claude claude Bot mentioned this pull request Sep 12, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from f769cd4 to 70c10e2 Compare September 12, 2026 06:16
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 70c10e2 to c26a619 Compare September 12, 2026 12:14
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 3465cda to 5093a2c Compare September 13, 2026 18:13
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 5093a2c to 8f6bea0 Compare September 14, 2026 00:30
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 8f6bea0 to 570325d Compare September 14, 2026 06:23
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 570325d to a1c9e50 Compare September 14, 2026 12:17
@github-actions
github-actions Bot force-pushed the changeset-release/main branch 3 times, most recently from 050205e to 76fd757 Compare September 15, 2026 00:28

Copy link
Copy Markdown
Collaborator

⏰ Standing note before this is merged: one of the 313 changesets below is pending an in-flight correction, and merging consumes it as-written

domain:spec execution PM seat, session_01KB5PFtxuy1x3dcR5gxudx6, 2026-09-15T01:27Z. ⛔ Informational only — I do not merge Version Packages PRs and am not asking anyone to hold this one. I am putting the fact where the click is, because until now it lived only on #17396's thread, which nobody reads on the way to this button.

The fact, measured on this PR at 2026-09-15T01:27Z

reading command result
this PR's file set GET /pulls/17076/files, 5 pages 473 files, 313 of them .changeset/*
the file in question same listing .changeset/schedule-trigger-acting-organization.md — status removed ⇒ this PR consumes it
is it still unconsumed on main git show origin/main:.changeset/schedule-trigger-acting-organization.md present, four minor bumps, banner intact
the correcting delivery GET /pulls/18198 open, draft — not landed

Why consuming it as-written is one-way

That changeset is the release note for #16659 / ruling G — a time-triggered flow declaring its acting organization. Ruling G requires its banner be rewritten before it ships; PR #18198 is the delivery that rewrites it. The rewrite has to happen while the changeset is still a changeset. Once this PR merges, the note is consumed into a published CHANGELOG.md and a released version, and there is no in-place correction of a shipped release note — the window does not reopen. That is why it is worth 30 seconds of someone's attention here rather than a note on another card.

This is also exactly why Check Changeset is deliberately red on #18198 and must stay red: its subject is this one file and nothing else. A green there would mean the correction had been abandoned.

What is actually being asked of a human — and what is not

Not "hold this PR". Release timing is the maintainer's call and always was; this seat has no standing to slow a release and is not trying to. The only thing I can honestly say is what the two orders of events produce:

A separate, already-standing maintainer item is the one that actually gates #18198: whether .changeset/schedule-trigger-acting-organization.md may be corrected in place at all. That question was put to the maintainer on #17396 (comment 5666913348, and restated at 5671221183) and has no answer on record as of this reading. So #18198 cannot land on this seat's initiative either — it is waiting on the same person. I am not re-asking it here; I am recording that both halves point at one decision.

Refs: #17396 (the card) · #18198 (the correcting delivery, open draft) · #16659 (ruling G)


Generated by Claude Code

Copy link
Copy Markdown
Collaborator

Sequencing note (director seat, 2026-09-16T05:46Z): per the maintainer's 「18198 确认 + A」 on PR #18198, that PR lands before this Version Packages PR is merged — one of the changesets inside this PR (.changeset/schedule-trigger-acting-organization.md, #16659) is corrected in place by #18198, and the correction is a same-window narrowing only while that order holds. The merge of this PR is the maintainer's own act; this note is the pointer, ⛔ not a hold written into any state.


Generated by Claude Code

@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 5ed957c to 90c0dab Compare September 16, 2026 12:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants