Skip to content

chore: release packages - #3133

Merged
os-zhuang merged 1 commit into
mainfrom
changeset-release/main
Aug 3, 2026
Merged

chore: release packages#3133
os-zhuang merged 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actionsgithub-actionsBot commented Aug 1, 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 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

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

@object-ui/console@17.2.0

@object-ui/app-shell@17.2.0

@object-ui/auth@17.2.0

@object-ui/collaboration@17.2.0

@object-ui/components@17.2.0

@object-ui/core@17.2.0

@object-ui/data-objectstack@17.2.0

@object-ui/fields@17.2.0

@object-ui/i18n@17.2.0

@object-ui/layout@17.2.0

@object-ui/mobile@17.2.0

@object-ui/plugin-charts@17.2.0

@object-ui/plugin-chatbot@17.2.0

@object-ui/plugin-detail@17.2.0

@object-ui/plugin-form@17.2.0

@object-ui/plugin-grid@17.2.0

@object-ui/plugin-list@17.2.0

@object-ui/plugin-timeline@17.2.0

@object-ui/providers@17.2.0

@object-ui/react@17.2.0

@object-ui/runner@17.2.0

@object-ui/sdui-parser@17.2.0

@object-ui/types@17.2.0

@object-ui/cli@17.2.0

@object-ui/permissions@17.2.0

@object-ui/plugin-ai@17.2.0

@object-ui/plugin-calendar@17.2.0

@object-ui/plugin-dashboard@17.2.0

@object-ui/plugin-designer@17.2.0

@object-ui/plugin-editor@17.2.0

@object-ui/plugin-gantt@17.2.0

@object-ui/plugin-kanban@17.2.0

@object-ui/plugin-map@17.2.0

@object-ui/plugin-markdown@17.2.0

@object-ui/plugin-report@17.2.0

@object-ui/plugin-tree@17.2.0

@object-ui/plugin-view@17.2.0

@object-ui/create-plugin@17.2.0

@object-ui/react-runtime@17.2.0

object-ui@17.2.0

@vercel

vercelBot commented Aug 1, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
ProjectDeploymentActionsUpdated (UTC)
objectuiIgnoredIgnoredAug 3, 2026 3:52am

Request Review

@github-actions
github-actionsBotforce-pushed the changeset-release/main branch 29 times, most recently from 352e351 to 18f6f4eCompareAugust 2, 2026 12:52
@github-actions
github-actionsBotforce-pushed the changeset-release/main branch 13 times, most recently from f9f9683 to 1aabeceCompareAugust 2, 2026 20:56
@github-actions
github-actionsBotforce-pushed the changeset-release/main branch from 1aabece to 6da21f3CompareAugust 3, 2026 03:52
@os-zhuang
os-zhuang added this pull request to the merge queueAug 3, 2026
Merged via the queue into main with commit ca58e45Aug 3, 2026
2 checks passed
@os-zhuang
os-zhuang deleted the changeset-release/main branch August 3, 2026 04:24
akarma-synetal pushed a commit to akarma-synetal/objectui that referenced this pull request Aug 3, 2026
…ai#3237)
Four changesets scored `major` — 17 package entries across objectui#3159,
objectui#3160, objectui#3161 and objectui#3225. Every publishable package
sits in one `fixed` group (39 packages), and changesets applies the group's
highest bump to all of it, so those entries staged the whole family as
`18.0.0` on the open release PR (objectstack-ai#3133) while `@objectstack/spec` is still
`^17.0.0-rc.1`.
objectui's major is pinned to the `@objectstack` major so that "same major ⇒
compatible" holds across the two repos; our own breaking changes ship as
`minor` with the break spelled out in the changeset body (AGENTS.md
§版本号策略). All four are rescored `minor` and each now carries the note
saying why — nothing about the described breaks changes, only the number
they would publish under.
The rule was already written and nothing executed it, and no workflow even
looked at a changeset: `ci.yml` and `lint.yml` both list `'**/*.md'` and
`.changeset/**` under `paths-ignore`, so a PR adding only a changeset starts
nothing. So it is mechanical now, in two places:
- `scripts/check-changeset-no-major.mjs` (dependency-free — the CI job is a
checkout plus one `node` call) exits non-zero on any `major` in changeset
frontmatter, and prints the file:line and the fix. The release that follows
objectstack across ITS major sets `OBJECTUI_ALLOW_MAJOR=1`.
- `.github/workflows/changeset-guard.yml` runs it on the inverse trigger of
every other workflow: only when `.changeset/**` changes.
- `pnpm test` asserts the same repository state, so the rule survives that
workflow being skipped or removed.
Claude-Session: https://claude.ai/code/session_01R8TU2mGotfDRNhg7WP5esH
Co-authored-by: Claude <noreply@anthropic.com>
Sign up for freeto 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.

1 participant

@os-zhuang