Mitchell Hashimoto d231e94535 Snap: Do not leak snap variables or snap paths into children (#8771) ... Avoid leaking snap environment values and in particular the `$SNAP*` values to the children that we run from the terminal. Do this programmatically instead of the launcher, since ghostty needs know the environment it runs in, while it must not leak the info to the children. We've also another leak on snap, that creates a more visible problem (wrong matching of children applications) that is the apparmor security profile. I've handled it at cc3b46f600 but that requires some love in order to fully decouple the snap option to the build, to avoid including it in non-snap builds, so an help would be appreciated there. > This PR was contains code (in `filterSnapPaths`) that was improved by DeepSeek.		2025-09-29 12:58:24 -07:00
..
DISCUSSION_TEMPLATE	update applied label to proper name	2025-05-05 21:37:49 -05:00
ISSUE_TEMPLATE	Update the pre-approved issue template	2024-12-28 18:37:17 -08:00
scripts	ci: do not run release tip workflow if corresponding commit released	2025-09-06 20:20:14 -07:00
workflows	Snap: Do not leak snap variables or snap paths into children (#8771)	2025-09-29 12:58:24 -07:00
dependabot.yml	Create dependabot.yml	2022-11-17 10:21:31 -08:00
pinact.yml	pin GitHub Actions to specific SHAs	2025-07-06 06:59:50 -07:00