chore(deps): upgrade @objectstack 7.4.1 → 7.7.0 (+ 7.6/7.7 migration)#366
Merged
Conversation
Bumps all @objectstack/* packages to 7.7.0 (latest), via 7.6 → 7.7.
7.7 ships the fixes for the three platform issues filed during this
upgrade (all verified resolved end-to-end):
- framework#1532 — sys_audit_log "no column named organization_id"
(audit writes now persist instead of failing on every mutation)
- framework#1533 — CLI hardcoded `logger:{level:'silent'}`
(now honors OS_LOG_LEVEL / LOG_LEVEL / --log-level)
- framework#1534 — strict CEL on string-serialized numeric fields
(rating/currency now hydrate; bare `record.x` comparisons work)
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
7.6 (ADR-0032):
- Replace the removed `type:'unique'` validation with unique indexes
(account.name, contact.email).
- Fix crm_campaign_member validation referencing nonexistent fields
(record.lead/contact → record.crm_lead/crm_contact) — surfaced by the
new schema-aware build validator.
7.7 (object-schema breaking changes):
- Remove `workflows[]` (no longer a valid object key). Field-update rules
migrated into existing *.hook.ts before-hooks:
account → last_activity_date on owner/type change
case → is_closed / closed_date / resolution_time_hours
opportunity → forecast_category by stage
task → is_completed / is_overdue
- Move top-level `trackHistory` under `enable` (campaign_member, line items).
- Drop `shareModel:'controlled-by-parent'` (sharingModel enum dropped it;
master-detail children inherit the master's sharing).
- Replace top-level `stateMachines` with a `type:'state_machine'`
validation rule (lead status, opportunity stage); delete the now-unused
lead.state.ts / opportunity.state.ts XState configs.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…y severity
Migrate the scheduled/notification object workflows[] (removed in 7.7) to
first-class flows:
- scheduled: campaign-completion, quote-expiration, contract-expiration
- record_change notify: contact-welcome, opportunity-won-alert,
task-urgent-alert
(lead high-score and case critical/escalation notifications were already
covered by lead_assignment / case_escalation and are not duplicated.)
Also in this round:
- Conditions are bare CEL (`record.rating >= 4`, `record.amount > 100000`).
These are validated as CEL at build time, and the 7.7 numeric-hydration
fix (framework#1534) makes the string-serialized rating/currency fields
compare correctly at runtime — no `double()` cast needed.
- case_escalation: also set `escalation_reason` when flipping
`is_escalated` true, or the object's `escalation_reason_required`
validation rejects the write and the flow aborts.
- Fix invalid notify `severity:'high'` across 6 flows → valid
`sys_notification` enum (info|warning|critical). 'high' silently failed
the notification insert, so the alert was never created even though the
flow fired.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Adds .claude/launch.json with a `crm-app` entry (objectstack dev, :4001) so the CRM Console (/_console/) can be launched as the preview server. (settings.local.json is intentionally left untracked — machine-local.) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
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
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.
Summary
Upgrades
@objectstack/*from 7.4.1 → 7.7.0 (via 7.6), resolves every breaking change across both releases, and verifies the platform behaves end-to-end. Closes #365.7.7 also ships the fixes for the three platform issues filed from this app during the upgrade — all re-tested and confirmed resolved:
sys_audit_log"no column named organization_id" → audit writes now persist (0 errors, rows written incl.crm_lead).logger:{level:'silent'}→ now honorsOS_LOG_LEVEL/LOG_LEVEL/--log-level.rating/currencynow hydrate; barerecord.xcomparisons work (thedouble()workaround is removed).Breaking changes handled
7.6 (ADR-0032):
type:'unique'validation removed → unique indexes (account.name,contact.email).crm_campaign_membervalidation referencing nonexistent fields (record.lead/contact→record.crm_lead/crm_contact).{…}braces).7.7 (object schema):
workflows[]removed from object schemas → field-update rules folded into the existing*.hook.tsbefore-hooks (accountlast_activity_date; caseis_closed/closed_date/resolution_time_hours; opportunityforecast_category; taskis_completed/is_overdue).campaign-completion,quote-expiration,contract-expiration(scheduled);contact-welcome,opportunity-won-alert,task-urgent-alert(record_change). Already-covered ones (lead high-score, case critical) were not duplicated.trackHistory→enable.trackHistory;shareModel:'controlled-by-parent'dropped (master-detail children inherit master sharing); top-levelstateMachines→type:'state_machine'validation rule (lead status, opportunity stage),*.state.tsdeleted.Bug fixed (surfaced by testing)
Notify nodes used
severity:'high', which is not a validsys_notification.severity(info|warning|critical) — the notification insert silently failed, so alerts were never created even though the flow fired. Fixed across 6 flows (4 pre-existing + 2 new) to valid values.Verification
tsc --noEmit+objectstack buildgreen (16 flows / 15 objects).lead_assignmentstampsnext_followup_date;opportunity_approval→ pending + suspended approval run;case_escalationescalates;case_csat_followupsuspends on wait.contact_welcome,urgent_task,large_deal_won), 0 insert failures.🤖 Generated with Claude Code