Uh oh!
There was an error while loading. Please reload this page.
chore(release): sys_department system-object rename is a breaking major (9.x → 10.0.0) - #2116
Merged
Merged
Conversation
fix(registry): silence bare-name collision warnings; keep display owners (#1855) objectui@70a56e15152c6e9ff602a9ff3675900e410531d7
…ng major (10.0.0) ADR-0057 D2 renames the shipped system object `sys_department` → `sys_business_unit` (object + `sys_department_member` → `sys_business_unit_member`, fields, i18n) with no compatibility alias. A renamed shipped system object is a breaking change to the platform's public data surface, so `@objectstack/platform-objects` and `@objectstack/plugin-sharing` move from `minor` to `major` — taking the 73-package fixed group from 9.11.0 to 10.0.0 on the next `changeset version`. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Uh oh!
There was an error while loading. Please reload this page.
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What
ADR-0057 D2 renames the shipped system object
sys_department→sys_business_unit(object + member tablesys_department_member→sys_business_unit_member, fields, i18n) with no compatibility alias. The change already landed in #2084; its changeset was filed asminor.This PR re-grades that release as a major: a renamed shipped system object is a breaking change to the platform's public data surface, so the version number must say so rather than riding inside a
minor.Change
.changeset/adr-0057-erp-authz.md:@objectstack/platform-objectsminor→major(ships the renamedsys_business_unitobject)@objectstack/plugin-sharingminor→major(member table + graph service + recipient)minor(the rename doesn't break their surface)**BREAKING:**note to the changelog body documenting the rename + migration requirement.Version impact
The published packages are a 73-member
fixedchangeset group anchored at@objectstack/spec(currently9.11.0). Marking any membermajortakes the entire group9.11.0→10.0.0on the nextchangeset version— including packages unrelated to the rename. This release was otherwise slated for9.12.0.Note / follow-up
This is a pure changeset re-grade — no migration path is added here. Deployments holding
sys_departmentrows, or metadata referencing the object by name, will break on upgrade. A data-migration step and/or transitional read alias can be a follow-up if we want a softer landing. Verified per ADR-0059's pre-publish hotcrm gate: no published downstream consumer references the old name.🤖 Generated with Claude Code