Uh oh!
There was an error while loading. Please reload this page.
docs(releases): source v12–v14 Console sections from real objectui commit ranges - #2830
Merged
Merged
Conversation
…nges Now that the objectui repo is available, replace the inferred Console (Studio) sections with per-commit frontend detail pulled via scripts/objectui-range.mjs over each major's bundled .objectui-sha range (resolved from the spec version tags): v12 = 77826989..b0aa2512 (58 commits), v13 = b0aa2512..397dcad7 (12), v14 = 397dcad7..6fa8e6ae (9). Each section leads with the reproducible SHA range and notes the frontend/backend phase offset (e.g. the enable.* Attachments UI shipped in the 13.x console, a release ahead of the v14 backend gates). Ratchet the role-word baseline down (v13 17→15, v14 7→9→7) since the corrected copy drops several "role" mentions. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SXFPRKA2ixrZmRFwK7Cxh6
The latest updates on your projects. Learn more about Vercel for GitHub.
|
os-zhuang
marked this pull request as ready for review
July 11, 2026 07:51
Uh oh!
There was an error while loading. Please reload this page.
os-zhuang added a commit
that referenced
this pull request
Jul 27, 2026
… bump type (#3528) (#3558) `@objectstack/console` ships a PREBUILT objectui SPA pinned by `.objectui-sha`, so a merged objectui fix is not live for anyone until that pin moves — the release pipeline clones objectui at the pin, builds it, and publishes the dist alongside the framework. The screen-flow fixes for #3528 landed in objectui (#2830, #2833) and were stranded there. This bumps the pin from cf2d56e32a11 to 2cb8d78e24ad so they ship, along with everything else merged frontend-side since the last refresh. Also fixes the bump-type detection in scripts/bump-objectui.sh, which decides whether a refresh is a minor or a patch. It tested the range with `git log --format=%s A..B | grep -qiE '^feat'`, but under `set -o pipefail` `grep -q` exits on the first match and the still-writing `git log` takes SIGPIPE, so the pipeline returned 141 and the test ALWAYS fell to the else branch. Every refresh was silently stamped `patch`, feature ranges included — this range has 20+ `feat` commits and was about to be stamped `patch` too. Counting with `grep -c` drains the input, so there is no signal and the count is truthful. Verified: with the fix the same invocation now writes `"@objectstack/console": minor`. `check:console-sha` passes (no dist in this checkout — nothing to drift against); the pinned commit is objectui `main`, which its own CI builds on every PR. Claude-Session: https://claude.ai/code/session_01LX9ut3MK3KykE11S9bJmv5 Co-authored-by: Claude <noreply@anthropic.com>
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.
Summary
Follow-up to #2827. That PR wrote the v12–v14 Console (Studio) sections from the companion-objectui notes embedded in the framework changesets, because
objectuiwasn't in scope. It now is — so this replaces those inferred sections with per-commit frontend detail pulled straight from objectui, using thescripts/objectui-range.mjstool #2827 added.How the ranges were derived
Each major's bundled objectui range comes from the
.objectui-shapinned at that major's release, resolved via the@objectstack/spec@N.0.0version tags (framework unshallowed to recover them):77826989..b0aa2512b0aa2512..397dcad7397dcad7..6fa8e6aeWhat changed
/:objectName/databare surface, URL-driven detail tabs, per-user list filters,visibleWhenoptions, import-wizard mappings, a data-invalidation bus.{ permissionSet }gating, and theenable.*Attachments / feeds-activities frontend (bundled a release ahead of the v14 backend gates).relationshipValueFieldposition panels (aligned to 14.3), phone-OTP login + SMS reset (framework#2780 frontend), the object Capabilities section, effective-holders list, dynamic branding, AI model-status panel.Each section leads with its reproducible SHA range and notes the frontend/backend phase offset. The role-word baseline ratchets down (v13 17→15, v14 9→7) since the corrected copy drops several "role" mentions.
Notes
check:role-wordratcheted,check:doc-authoring,check:release-notes). No bare{…}outside code spans.🤖 Generated with Claude Code
https://claude.ai/code/session_01SXFPRKA2ixrZmRFwK7Cxh6
Generated by Claude Code