Repository navigation
docs: beta.1 release notes - #3214
Merged
Merged
Conversation
Co-authored-by: capy-ai-staging[bot] <305915985+capy-ai-staging[bot]@users.noreply.github.com>
…back into a fresh data folder Co-authored-by: capy-ai-staging[bot] <305915985+capy-ai-staging[bot]@users.noreply.github.com>
…tity Co-authored-by: capy-ai-staging[bot] <305915985+capy-ai-staging[bot]@users.noreply.github.com>
Co-authored-by: capy-ai-staging[bot] <305915985+capy-ai-staging[bot]@users.noreply.github.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 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.
Adds the release notes for v2.0.0-beta.1 as a docs page, and brings the beta.1 fact sheet up to date with what merged from November 6 to 13 (#3203 to #3213).
Release notes (
docs/core/release-notes/beta-1.mdx, listed under Developer after Releases). The same text is meant to be the body of the GitHub release. It covers whatreleases.mdxsays the notes must state: supported platforms and filesystems, schema and storage changes, known limits, security changes, behavior that can change file bytes, and backup steps before upgrading. It also states that beta.1 is Linux and macOS only, with Windows in the nightly; that it replaces 0.4.3 as Latest and links 0.4.3 for the v1 app; that the extension runtime is not included; how to install the desktop.dmgand.deb, the CLI and daemon, and the server tarball; and that the desktop updater is on.releases.mdxnow links the page from Publishing.Fact sheet (
docs/plans/2026-11-05-beta1-release-notes-facts.md): a new section for #3203 to #3213, the desktop updater and its key change, and answers to the open items.The notes depend on one finding. alpha.2 kept its data in the platform data folder (
~/Library/Application Support/spacedrive,~/.local/share/spacedrive). beta.1 uses~/.spacedriveand never reads the old path. So beta.1 does not open an alpha.2 library on its own, and the alpha.2 data stays as it was. The notes tell alpha.2 users to start a new library and add their folders again. The alpha.2 desktop app can't install beta.1 through its updater, because alpha.2 trusts updater key053A7DF33374C68Band beta.1 is signed withFA1DB2E94E74028C.The Updates section describes the in-app updater from #3215. It checks at startup and every six hours, and offers Install and restart. Known limits add two cases: on Linux, an update fails without a polkit agent, and a daemon running as a service keeps the old version until you restart it.
Also adds a register row to
PROJECT_STATUS.md.