Repository navigation
feat(cli)!: os package publish defaults visibility to org (ADR-0007 ②) - #1700
Merged
Merged
Conversation
A freshly published package should be auto-visible/installable across the owner organization's environments — that's the common "build an app, deploy it to my envs" case. Default `--visibility` private → org. Publishers opt into narrower `private` (grant/ACL) or public `marketplace` explicitly. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
hotlong
pushed a commit
that referenced
this pull request
Sep 4, 2026
…rade entry page (#15322) Two releases shipped with no upgrade guidance, and the customer's entry page reads a breaking upgrade as a tag swap. content/docs/upgrading.mdx - The per-major checklist table listed v17 once, pointing at 17.0.0. A deployment on 17.1.0 got no pointer to either release it has to cross. The section becomes "Per-release specifics" and carries a row per v17 release. - The page's framing ("move the tag, restart") plus the metadata-compatibility Callout read together as "a minor is a no-op". A second Callout scopes the first: the major boundary promises metadata compatibility and nothing else. The two-upgrades-two-clocks argument is untouched. content/docs/releases/v17.mdx - New "What's new in 17.2.0" and "What's new in 17.3.0" detail sections, in the shape 17.0.0/17.1.0 establish. Content is reused from the packages' own CHANGELOG entries rather than paraphrased; every entry is cited by changeset hash. - Release-status blockquote now says 17.3.0 is current, and names what makes 17.3.0 a minor by number only. - "Upgrade checklist" and "References" are promoted from h3 to h2 so they stay page-level sections after two more release sections are appended. No published prose in the 17.0.0 / 17.1.0 sections is changed; the #upgrade-checklist, #1700 and #1710 anchors are preserved. The consolidated 17.1.0 -> 17.3.0 upgrade checklist is deliberately NOT in this commit: it is blocked on hotcrm#1576's documentation-first upgrade log, and a checklist step nobody has run is worse than a missing one. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UHvF5hyiZjnCyExFnfQB8m
akarma-synetal
pushed a commit
to akarma-synetal/framework
that referenced
this pull request
Sep 9, 2026
…rade entry page (objectstack-ai#15322) (objectstack-ai#15333) Two releases shipped with no upgrade guidance, and the customer's entry page reads a breaking upgrade as a tag swap. content/docs/upgrading.mdx - The per-major checklist table listed v17 once, pointing at 17.0.0. A deployment on 17.1.0 got no pointer to either release it has to cross. The section becomes "Per-release specifics" and carries a row per v17 release. - The page's framing ("move the tag, restart") plus the metadata-compatibility Callout read together as "a minor is a no-op". A second Callout scopes the first: the major boundary promises metadata compatibility and nothing else. The two-upgrades-two-clocks argument is untouched. content/docs/releases/v17.mdx - New "What's new in 17.2.0" and "What's new in 17.3.0" detail sections, in the shape 17.0.0/17.1.0 establish. Content is reused from the packages' own CHANGELOG entries rather than paraphrased; every entry is cited by changeset hash. - Release-status blockquote now says 17.3.0 is current, and names what makes 17.3.0 a minor by number only. - "Upgrade checklist" and "References" are promoted from h3 to h2 so they stay page-level sections after two more release sections are appended. No published prose in the 17.0.0 / 17.1.0 sections is changed; the #upgrade-checklist, objectstack-ai#1700 and objectstack-ai#1710 anchors are preserved. The consolidated 17.1.0 -> 17.3.0 upgrade checklist is deliberately NOT in this commit: it is blocked on hotcrm#1576's documentation-first upgrade log, and a checklist step nobody has run is worse than a missing one. Claude-Session: https://claude.ai/code/session_01UHvF5hyiZjnCyExFnfQB8m Co-authored-by: Claude <noreply@anthropic.com>
This branch was successfully deployed
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
1 participant
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.
Per ADR-0007 decision ②: a published package should be auto-visible/installable across the owner org's environments by default.
os package publish --visibilitydefault private → org. Publishers opt intoprivate(grant/ACL) ormarketplace(public) explicitly. Pairs with cloud #191.🤖 Generated with Claude Code