Resolve remaining Expo/Jest transitive security advisories after SDK 57 upgrade

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

维护者通常 1 天内回复

@issdn 已经在做这个了。

开始于 2026年10月8日。

评估

这个 Issue 还没有评估数据。

描述

Follow-up to PR #318, merged in 9dfc22bf. Refs #304.

Small code fixes

  • Replace the deprecated unstable_settings.initialRouteName in mobile-app/app/_layout.tsx with anchor.
  • Add locker-backend/public/js/app/ to .gitignore. filament:assets generates it and the image build regenerates it.

Decisions

  • Accept the remaining advisories as build-time risk, or object here. Both are in Expo CLI tooling and not in the shipped app. Rechecked on 2026-10-30: backend and locker client report none, and mobile reports these two.
    • zod 3.25.76, high (GHSA-mrhx-c7xc-m3w5): the latest @expo/cli (58.1.17) still requires ^3.25.76, and the fix exists only in zod ≥4.6.6. Do not force zod 4 onto @expo/cli.
    • deepmerge 4.3.1, low (GHSA-gcqx-w48m-w2h4): no patched release.
    • Recheck both at the next Expo SDK upgrade. No separate tracking is needed.
  • Decide what to do about react-native-render-html, the only Expo Doctor failure (19/20 pass). It is used only by the terms screen. Replace it only if there is a concrete reason.

Moved out of this issue

  • Sail setup (APP_USER=www-data is missing from .env.example, and a fresh checkout needs www-data access to storage, bootstrap/cache, public and .env): own issue, not related to this upgrade.
  • Admin compartment list keeps the closed badge until refresh: own issue, if the behaviour should change.
  • Stuck open requests and the simulator freeze on piped stdin: #345.

Done when

  • The small code fixes are merged.
  • The decisions above are recorded here.
  • #304, #305 and #306 are closed if nothing else is pending there.
主要语言
PHP
星标
26
派生
2
平均合并
2 天 6 小时
30 天内合并 PR
14

环境准备

在 Codespaces 中打开

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

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 没有贡献指南

从这里开始

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

Open-Locker/Open-Locker 的其他 Issue

查看 Open-Locker/Open-Locker 的全部 Issue

相似的 Issue

更多 PHP Issue

把新 issue 发到你的邮箱

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