Repository navigation
chore: release package(s) - #392
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
October 18, 2026 19:12
5d13ef0 to
858662e
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 19, 2026 09:07
858662e to
74a4cd8
Compare
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
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish 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
@internal/docs@0.10.0
Minor Changes
e215250Thanks @theogravity! - Make dashboard information easier to scan with consistent labels, readable values, and wrapping for long paths and addresses. Keep conditional fields beneath their selected radio option, disable Save for unchanged drafts, and clarify warnings and validation. Apply the shared fact styling to the node dashboard as well. On the docs site, the SSH destination-confirmation guide and its screenshot now match the always-visible fingerprint.Patch Changes
#395
af7deeeThanks @theogravity! - Replace the crowded sidebar with a mini rail for app sections and a contextual sidebar for their pages. Workspaces show only the selected workspace’s subshells, with a workspace switcher and the existing pane actions. Settings, account pages, and mobile setup each have their own navigation, including on phones.Keep the final workspace tab in place when removing panes, with an explanation on the disabled close control and an API guard for concurrent removals.
#393
4844badThanks @theogravity! - Document sharing agent and SSH presets, access levels, secret disclosure, revocation behavior, and version 1 preset export/import.#394
67c1d73Thanks @theogravity! - Workspaces are now the default home for panes. Launches land as tabs in the workspace you're viewing (or a fresh one from the landing page), Split creates a real named workspace instead of a draft, and a workspace retires itself when its last pane is removed. The sidebar's Workspaces tree lists each workspace's panes (unfiled sessions stay in the subshells list), and opening the app returns to the workspace you were last in. Drafts, the discard sweep, and the unsaved/saved split are gone:GET /api/workspacesnow carries every workspace with its panes, adding a pane twice is idempotent, andPOST /api/subshellsaccepts aworkspaceId. Migration 0058 drops the draft column and adds the unique pane constraint.The same move finishes on the surface: the page bar above the panes is now the FOCUSED PANE's subshell header (dot, in-place rename, directory, disclosures, its ⋯ menu), and the workspace's name edits from the rail's context menu (
Rename…). You are always in a workspace: a launch raised with none on screen joins a workspace that exists (the last one you visited, else the most recent), opening a fresh one only when the instance has none, a plain click on a rail row means its tab (focus, its holder, or filing it into an existing workspace), and the Workspace/Others pseudo-groups in the subshell list are gone. Tree pane rows are the same component as the list's rows, wearing the shared status dot and their working directory, and a workspace row is a drop target: dragging a session onto it says "Add to workspace" and files it there.@internal/server@2.4.0
Minor Changes
#395
af7deeeThanks @theogravity! - Replace the crowded sidebar with a mini rail for app sections and a contextual sidebar for their pages. Workspaces show only the selected workspace’s subshells, with a workspace switcher and the existing pane actions. Settings, account pages, and mobile setup each have their own navigation, including on phones.Keep the final workspace tab in place when removing panes, with an explanation on the disabled close control and an API guard for concurrent removals.
#393
4844badThanks @theogravity! - Share agent and SSH presets with individual users or everyone on the instance. View access allows inspection, use, and cloning; Edit access also allows changes. Sharing and deletion remain owner-only, and using a shared preset still requires node and SSH permissions.Export presets as versioned .preset JSON files and import validated files as new private copies, with name and node choices available before saving.
#394
67c1d73Thanks @theogravity! - Workspaces are now the default home for panes. Launches land as tabs in the workspace you're viewing (or a fresh one from the landing page), Split creates a real named workspace instead of a draft, and a workspace retires itself when its last pane is removed. The sidebar's Workspaces tree lists each workspace's panes (unfiled sessions stay in the subshells list), and opening the app returns to the workspace you were last in. Drafts, the discard sweep, and the unsaved/saved split are gone:GET /api/workspacesnow carries every workspace with its panes, adding a pane twice is idempotent, andPOST /api/subshellsaccepts aworkspaceId. Migration 0058 drops the draft column and adds the unique pane constraint.The same move finishes on the surface: the page bar above the panes is now the FOCUSED PANE's subshell header (dot, in-place rename, directory, disclosures, its ⋯ menu), and the workspace's name edits from the rail's context menu (
Rename…). You are always in a workspace: a launch raised with none on screen joins a workspace that exists (the last one you visited, else the most recent), opening a fresh one only when the instance has none, a plain click on a rail row means its tab (focus, its holder, or filing it into an existing workspace), and the Workspace/Others pseudo-groups in the subshell list are gone. Tree pane rows are the same component as the list's rows, wearing the shared status dot and their working directory, and a workspace row is a drop target: dragging a session onto it says "Add to workspace" and files it there.Patch Changes
e215250Thanks @theogravity! - Make dashboard information easier to scan with consistent labels, readable values, and wrapping for long paths and addresses. Keep conditional fields beneath their selected radio option, disable Save for unchanged drafts, and clarify warnings and validation. Apply the shared fact styling to the node dashboard as well. On the docs site, the SSH destination-confirmation guide and its screenshot now match the always-visible fingerprint.@internal/desktop-client@1.3.2
Patch Changes
e215250]:@internal/node@2.1.3
Patch Changes
e215250Thanks @theogravity! - Make dashboard information easier to scan with consistent labels, readable values, and wrapping for long paths and addresses. Keep conditional fields beneath their selected radio option, disable Save for unchanged drafts, and clarify warnings and validation. Apply the shared fact styling to the node dashboard as well. On the docs site, the SSH destination-confirmation guide and its screenshot now match the always-visible fingerprint.@internal/desktop-server@1.5.3
Patch Changes
af7deee,4844bad,e215250,67c1d73]: