Skip to content

OpenPipal 1.1.2

Choose a tag to compare

View all tags
@yuanlang12 yuanlang12 released this 06 Sep 11:05
· 12 commits to main since this release
v1.1.2
e100b35

This release fixes two problems that hit people installing OpenPipal on a Mac for the first time.

What's fixed

  • "System sandbox not enabled" on a fresh Mac — the OS sandbox refused to start unless a ripgrep (rg) binary was already on your PATH, and most Macs don't have one. The agent then reported system sandbox not enabled and disabled shell execution entirely. OpenPipal now ships its own rg (from @vscode/ripgrep, MIT) and hands it to the sandbox directly, so the sandbox comes up on every Mac without installing anything. If you had worked around this with brew install ripgrep, you no longer need it.
  • Intel Macs: image reading, PDF rendering and artifact compilation — the x64 DMG of 1.1.1 was packaged on an Apple Silicon machine and carried the arm64 builds of esbuild, sharp, libvips and @napi-rs/canvas, which cannot load on an Intel Mac. The build now stages the correct architecture's binaries per DMG and a factory check verifies each package before release.

Windows installers are rebuilt from the same source; there are no Windows-specific changes in this release. There is still no OS sandbox on Windows (the agent asks before running shell commands).

Install

macOS (Apple Silicon: openpipal-1.1.2-arm64.dmg; Intel: openpipal-1.1.2-x64.dmg)
The build is ad-hoc signed. On first launch use System Settings → Privacy & Security → Open Anyway, or run xattr -dr com.apple.quarantine /Applications/OpenPipal.app.

Windows (most PCs: openpipal-1.1.2-x64-setup.exe; Snapdragon laptops: openpipal-1.1.2-arm64-setup.exe)
The installer is not code-signed, so SmartScreen shows "Windows protected your PC": click More info → Run anyway. It installs per-user into %LOCALAPPDATA%\Programs\OpenPipal. Install Git for Windows if you want the agent to run shell commands. On ARM64, PDF page rendering is unavailable (@napi-rs/canvas has no win32-arm64 build yet).

The browser extension (0.3.13) is unchanged from 1.0.0.

Verify what you installed

SHA256SUMS.txt covers every installer. On Windows, verify-windows-install.ps1 -ExpectedAsarSha256 <sha> proves the installed app is this build; the expected value is asarSha256 in the attached factory report for your architecture.

Assets 11
Loading