diff --git a/README.md b/README.md index bc993fd47..576d4d1f7 100644 --- a/README.md +++ b/README.md @@ -58,9 +58,9 @@ - **Web:** [try it in your browser][web-app], no install. ARM64 and 32-bit builds, portable zip, .deb, .rpm, Flatpak and the other packages are on the -[downloads page](docs/downloads.md). The downloads aren't signed yet: on Windows choose -**More info**, then **Run anyway** in SmartScreen; on macOS right-click SolidCraft and choose **Open** -the first time. On SolidCraft 0.11 to 0.14, download once by hand; see +[downloads page](docs/downloads.md). The macOS app is signed with a Developer ID and notarized by +Apple. The Windows downloads aren't signed yet: choose **More info**, then **Run anyway** in +SmartScreen. On SolidCraft 0.11 to 0.14, download once by hand; see [updating](https://docs.solidcraft.io/guide/updates.html#updating-from-011-to-014). ## What works diff --git a/crates/ui-egui/src/update.rs b/crates/ui-egui/src/update.rs index 11a46850f..3a134a1d3 100644 --- a/crates/ui-egui/src/update.rs +++ b/crates/ui-egui/src/update.rs @@ -29,14 +29,14 @@ use crate::theme::Tokens; use crate::ui_kit; /// The repository releases come from. -pub const REPO: &str = "bherbruck/solidcraft"; +pub const REPO: &str = "tangency-labs/solidcraft"; /// The one request an update check makes. -pub const LATEST_API: &str = "https://api.github.com/repos/bherbruck/solidcraft/releases/latest"; +pub const LATEST_API: &str = "https://api.github.com/repos/tangency-labs/solidcraft/releases/latest"; /// Where Download goes when no package fits this installation. -pub const RELEASES_PAGE: &str = "https://github.com/bherbruck/solidcraft/releases/latest"; -/// Release pages and assets must be on GitHub, under this repository. The repository is moving -/// to the `tangency-labs` organisation, so releases may name either owner (the API request stays -/// on the old name, which GitHub redirects after a transfer). +pub const RELEASES_PAGE: &str = "https://github.com/tangency-labs/solidcraft/releases/latest"; +/// Release pages and assets must be on GitHub, under this repository. The repository moved to the +/// `tangency-labs` organisation, so releases may still name either owner (older releases and the +/// links GitHub redirects keep the old one). const RELEASE_PREFIXES: [&str; 2] = ["https://github.com/bherbruck/solidcraft/releases/", "https://github.com/tangency-labs/solidcraft/releases/"]; /// A release page or asset URL: github.com, one of the two owners, exactly `solidcraft`, then diff --git a/crates/ui-egui/src/update/install.rs b/crates/ui-egui/src/update/install.rs index 8a88fafb2..b954475e9 100644 --- a/crates/ui-egui/src/update/install.rs +++ b/crates/ui-egui/src/update/install.rs @@ -14,9 +14,8 @@ //! - Windows portable `.zip` / standalone `.exe`: the running `solidcraft.exe` is renamed to //! `solidcraft.exe.old` (Windows allows renaming a running executable), the new one takes its //! name, and SolidCraft offers a restart; the `.old` file is deleted at the next start. -//! - macOS: the `.dmg` is verified and opened; the user drags the app to Applications. SolidCraft -//! is ad-hoc signed and not notarized, so replacing the bundle in place would install code the -//! system can't vouch for without the user seeing it. +//! - macOS: the `.dmg` is verified and opened; the user drags the app to Applications. The +//! bundle is never replaced in place from the background. //! - Flatpak, Snap, `.deb`, `.rpm`, `.tar.gz`: never replaced; the window shows the command. use std::io::{Read, Write}; diff --git a/docs/book/src/guide/assemblies.md b/docs/book/src/guide/assemblies.md index 0a67afe5a..859b38732 100644 --- a/docs/book/src/guide/assemblies.md +++ b/docs/book/src/guide/assemblies.md @@ -40,7 +40,7 @@ dimension parameters. Repeated child instances remain shared within the new copy appearances and wholly internal joints/motion records receive copied references. Design-wide user parameters remain shared; retained external links and omitted cross-boundary motion records are reported. Unsupported destructive links refuse the entire copy. See -[individual-instance and copy details](https://github.com/bherbruck/solidcraft/blob/main/docs/occurrence-workflows.md). +[individual-instance and copy details](https://github.com/tangency-labs/solidcraft/blob/main/docs/occurrence-workflows.md). **Extract to File** (`component.extract`, in a component's right-click menu) moves a component into a design of its own: its sketches, features, bodies, subcomponents and the joints among them @@ -407,7 +407,7 @@ uses its first placement; `occurrence.properties` selects a specific instance. R measures the complete assembly. Volumes are summed, including overlapping bodies, rather than measuring their union. The same workflow is available through `component.properties` and `occurrence.properties`; see -[placement and measurement details](https://github.com/bherbruck/solidcraft/blob/main/docs/assembly-properties.md). +[placement and measurement details](https://github.com/tangency-labs/solidcraft/blob/main/docs/assembly-properties.md). ## Part properties and the bill of materials diff --git a/docs/book/src/guide/files.md b/docs/book/src/guide/files.md index d91e6a08b..d257e619c 100644 --- a/docs/book/src/guide/files.md +++ b/docs/book/src/guide/files.md @@ -97,12 +97,12 @@ Closed mechanical meshes with a constant cross-section can be rebuilt as solids ordinary 3MF in which every triangle also names the B-rep face it lies on and every coordinate is the tessellation's own double-precision value. Meshing and analysis tools can use the tags to keep a model's faces (for loads, boundary conditions or feature edges); other 3MF readers ignore -them. The format is specified in [`docs/formats/3mf-face-tags.md`](https://github.com/bherbruck/solidcraft/blob/main/docs/formats/3mf-face-tags.md). +them. The format is specified in [`docs/formats/3mf-face-tags.md`](https://github.com/tangency-labs/solidcraft/blob/main/docs/formats/3mf-face-tags.md). **File → Export URDF…** (`file.export` with a `.urdf` path) writes the assembly for robot simulators and ROS: a link per component placement with its mesh, mass and inertia, and the assembly's joints, so the parts move in the simulator as they do in SolidCraft. The meshes are -written as STL files next to the `.urdf`. See [`docs/urdf.md`](https://github.com/bherbruck/solidcraft/blob/main/docs/urdf.md). +written as STL files next to the `.urdf`. See [`docs/urdf.md`](https://github.com/tangency-labs/solidcraft/blob/main/docs/urdf.md). Saves are atomic: a crash at any moment leaves either the old file or the new one, and the replaced version is kept as `.bak`. A save keeps the file's permissions, and a design diff --git a/docs/book/src/guide/getting-started.md b/docs/book/src/guide/getting-started.md index 77dbabe4f..86ff49ca4 100644 --- a/docs/book/src/guide/getting-started.md +++ b/docs/book/src/guide/getting-started.md @@ -2,17 +2,17 @@ The desktop executable is `solidcraft`, the CLI is `solidcraft-cli`, and designs are saved as `.sc` (`.solidcraft` designs from earlier releases still open, and Save keeps their name). Designs, settings and setups from builds released under the previous product name keep -working (see the [compatibility notes](https://github.com/bherbruck/solidcraft/blob/main/docs/compatibility.md)). +working (see the [compatibility notes](https://github.com/tangency-labs/solidcraft/blob/main/docs/compatibility.md)). ## Desktop Download the installer for your system from the -[Download section of the README](https://github.com/bherbruck/solidcraft#download) or the -[releases page](https://github.com/bherbruck/solidcraft/releases), or build it yourself with +[Download section of the README](https://github.com/tangency-labs/solidcraft#download) or the +[releases page](https://github.com/tangency-labs/solidcraft/releases), or build it yourself with stable Rust (1.95 or newer): ```sh -git clone https://github.com/bherbruck/solidcraft && cd solidcraft +git clone https://github.com/tangency-labs/solidcraft && cd solidcraft cargo run --release -p solidcraft -- --sample # opens with a sample part ``` @@ -24,18 +24,21 @@ cargo run --release -p solidcraft -- --sample # opens with a sample part Open the release `.dmg` and drag `SolidCraft.app` onto Applications. -The macOS build is signed ad-hoc and not notarized, so macOS blocks the first launch with -"SolidCraft can't be opened, because Apple can't verify if the app is vulnerable". Open -**System Settings › Privacy & Security**, scroll down to the message about SolidCraft, click -**Open Anyway** and confirm: the app opens normally from then on. From a terminal, remove the -quarantine flag instead: +The release `.dmg` is signed with a Developer ID and notarized by Apple, and the app and the disk +image carry the notarization ticket, so macOS opens SolidCraft normally, even offline. + +A copy you build yourself, or one from a fork that has no signing keys, is signed ad hoc and not +notarized, so macOS blocks its first launch with "SolidCraft can't be opened, because Apple can't +verify if the app is vulnerable". Open **System Settings › Privacy & Security**, scroll down to the +message about SolidCraft, click **Open Anyway** and confirm: the app opens normally from then on. +From a terminal, remove the quarantine flag instead: ```sh xattr -dr com.apple.quarantine /Applications/SolidCraft.app ``` When updating from a build released under the previous product name, follow the -[macOS upgrade notes](https://github.com/bherbruck/solidcraft/blob/main/docs/compatibility.md#macos) so you replace it rather than install a second copy. +[macOS upgrade notes](https://github.com/tangency-labs/solidcraft/blob/main/docs/compatibility.md#macos) so you replace it rather than install a second copy. ### Linux AppImage @@ -76,7 +79,7 @@ Earlier releases used the application IDs `ai.storyteller.solidcraft` and, up to `io.tangencylabs.solidcraft`; accept, and your settings and autosaves move with it. If you installed a `.flatpak` bundle, install the new bundle, launch it once (it copies your settings), then run `flatpak uninstall --user ai.storyteller.solidcraft` (or `ai.storyteller.solvecraft`; see the -[compatibility notes](https://github.com/bherbruck/solidcraft/blob/main/docs/compatibility.md#linux-app-id)). +[compatibility notes](https://github.com/tangency-labs/solidcraft/blob/main/docs/compatibility.md#linux-app-id)). Alternatively, download the release's `.flatpak` file for your architecture and run `flatpak install --user ./solidcraft-VERSION-linux-ARCH.flatpak`. The bundle supplies the @@ -108,7 +111,7 @@ part, `?webgl` forces WebGL2 where WebGPU is missing or misbehaves; the browser `?webgpu`, and an app installed from Chrome or Edge starts with it too). Designs are saved in the browser's private file storage, which needs HTTPS or localhost. Planned worker and tiered-storage integration is -described in [web-runtime.md](https://github.com/bherbruck/solidcraft/blob/main/docs/web-runtime.md) +described in [web-runtime.md](https://github.com/tangency-labs/solidcraft/blob/main/docs/web-runtime.md) (design; not yet wired in the shipped wasm build). After the first visit the web app works offline: the browser keeps a copy of it. Online, each @@ -358,7 +361,7 @@ name: the `solidcraft` and `solidcraft-cli` programs, `.solidcraft` designs (`.s environment variables, settings folders and the `solidcraft` MCP server. Upgrading keeps working: designs, settings, recovery files, environment variables and CLI/MCP setups from earlier builds carry over. Every compatibility shim is listed in the -[compatibility notes](https://github.com/bherbruck/solidcraft/blob/main/docs/compatibility.md). +[compatibility notes](https://github.com/tangency-labs/solidcraft/blob/main/docs/compatibility.md). Use the SolidCraft documentation and web-app URLs. GitHub redirects links to the renamed repository; old-name Pages and Flatpak URLs are not maintained as permanent aliases. diff --git a/docs/book/src/guide/parameters.md b/docs/book/src/guide/parameters.md index 1e148b064..75aa289d7 100644 --- a/docs/book/src/guide/parameters.md +++ b/docs/book/src/guide/parameters.md @@ -74,7 +74,7 @@ suppressed features, physical materials and body appearances, switched with `con The table's Library picker selects material or appearance values. Choose **Follow material** to clear an appearance override. Custom looks retain their colour and opacity across activation, undo and save/reopen. See -[configuration commands and examples](https://github.com/bherbruck/solidcraft/blob/main/docs/configurations.md). +[configuration commands and examples](https://github.com/tangency-labs/solidcraft/blob/main/docs/configurations.md). ## Checking a design across a parameter's range diff --git a/docs/book/src/guide/updates.md b/docs/book/src/guide/updates.md index 088cdd550..76df4de2e 100644 --- a/docs/book/src/guide/updates.md +++ b/docs/book/src/guide/updates.md @@ -37,11 +37,12 @@ Where SolidCraft can replace itself safely, the window also has **Update now**: Every download is verified before anything changes: its SHA-256 must match the release's `SHA256SUMS.txt`, fetched over HTTPS from the same release, and, once the project signs its releases, that list must carry a valid signature by SolidCraft's release key that names the -release (see [releasing](https://github.com/bherbruck/solidcraft/blob/main/docs/releasing.md#update-signing)). +release (see [releasing](https://github.com/tangency-labs/solidcraft/blob/main/docs/releasing.md#update-signing)). A download that doesn't verify is deleted and the installed copy is left as it was; **Download** still gets the package for a manual install. On macOS SolidCraft opens the disk image rather than -replacing the app itself, because the app is ad-hoc signed and not notarized: replacing it in the -background would install code macOS can't vouch for without you seeing it. +replacing the app itself: you drag the new app to Applications, as you did the first time. The +app and the disk image are signed with a Developer ID and notarized by Apple, so macOS opens the +new copy without a warning. Update now needs write access to the installed file: an AppImage in a folder you can't write to fails with a message, and **Download** is the way to update it. @@ -64,14 +65,14 @@ affected. One HTTPS request each time SolidCraft starts, and once a day while it stays open: ```text -GET https://api.github.com/repos/bherbruck/solidcraft/releases/latest +GET https://api.github.com/repos/tangency-labs/solidcraft/releases/latest User-Agent: SolidCraft-update-check Accept: application/vnd.github+json X-GitHub-Api-Version: 2022-11-28 ``` **Update now** then downloads `SHA256SUMS.txt` (and its signature) and the one package from the -release's own `github.com/bherbruck/solidcraft/releases/download/…` links, with the same +release's own `github.com/tangency-labs/solidcraft/releases/download/…` links, with the same User-Agent. That's all: no version number, no machine or user identifier, no usage data, no cookies. GitHub sees the request like any other visit to the API (your IP address, the time); see [GitHub's privacy statement](https://docs.github.com/site-policy/privacy-policies/github-general-privacy-statement). @@ -110,7 +111,7 @@ off. ## Which file Download gets -Releases attach the main packages under fixed names (see [releasing](https://github.com/bherbruck/solidcraft/blob/main/docs/releasing.md)), +Releases attach the main packages under fixed names (see [releasing](https://github.com/tangency-labs/solidcraft/blob/main/docs/releasing.md)), and SolidCraft picks the one matching how it was installed: | Installed as | Detected by | Download | How to update | diff --git a/docs/downloads.md b/docs/downloads.md index 779907af1..950e32eab 100644 --- a/docs/downloads.md +++ b/docs/downloads.md @@ -20,11 +20,11 @@ Every platform and package. The links point at the latest release. Windows releases will be code signed through the SignPath Foundation: free code signing provided by [SignPath.io](https://about.signpath.io/), certificate by [SignPath Foundation](https://signpath.org/). This is being set up; until it's live, the note -below applies. macOS releases are being set up to be signed with an Apple Developer ID and -notarized by Apple. +below applies. macOS releases are signed with an Apple Developer ID and notarized by Apple (the app +and the disk image carry the notarization ticket), so they open normally. -The downloads aren't signed yet. On Windows, if SmartScreen warns you, choose **More info**, then -**Run anyway**. On macOS, the first time, right-click SolidCraft in Applications and choose **Open**. +The Windows downloads aren't signed yet. If SmartScreen warns you, choose **More info**, then +**Run anyway**. **On SolidCraft 0.11 to 0.14?** Its **Update now** can't install 0.15.0 or later, because the releases moved to a new address. Download the new version once from the links above; after that,