Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

docs(macos): sandboxed vs non-sandboxed builds and the minimum macOS version

未关闭
#1,591 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
1-2 天
新手友好度
43/100
Issue 类型
文档
描述清晰度
基本清楚
活跃度
活跃
技术栈
dart, flutter
领域
desktop, devops

调研方向

Read docs/macos-signing.md, the README and contributor docs, then check the Xcode project’s Release.entitlements and MACOSX_DEPLOYMENT_TARGET settings. Determine how the sandboxed and signed builds differ and check the plugins’ macOS requirements. Done means the unsigned build behavior and limitations are documented or its sandbox choice is resolved, and the documented minimum macOS version matches the supported configuration.

由索引模型根据 Issue 内容生成。

描述

documentation P3

Problem

The shipped macOS app is one of two different programs depending on CI secrets:

  • Signed builds use ReleaseSigned.entitlements: no App Sandbox, hardened runtime.
  • Without MACOS_* secrets (forks, local flutter build macos) the Xcode project's Release.entitlements applies: App Sandbox on, only network.client/server and files.user-selected.read-write.

In the sandboxed build ~/.querya, extension processes (sandbox-exec inside a sandbox), in-place updates into /Applications, the MCP socket and previously chosen SQLite file paths (no security-scoped bookmarks) do not behave like the signed build. docs/macos-signing.md mentions it; README and the contributor docs do not.

Also MACOSX_DEPLOYMENT_TARGET = 10.15 in all configurations while the docs target macOS 14+ for ProMotion; the minimum is not checked against the plugins' requirements.

Tasks

  • Decide: ship the unsigned build without the sandbox too, or document the limitations in README / CONTRIBUTING.
  • Align and document the minimum macOS version.
主要语言
Dart
星标
23
派生
1
平均合并
31 分钟
30 天内合并 PR
570

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

QueryaHub/Querya-Desktop 的其他 Issue

查看 QueryaHub/Querya-Desktop 的全部 Issue

相似的 Issue

更多 Dart Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。