Hamza 35cc685e90 cli: an unconfined write still follows a symbolic link ...

Routing the CLI's writes through `file_access` changed what happens when the
output path is a symbolic link. `file_access::write` stages the bytes and
renames them into place, and a rename replaces the link with a regular file,
where `std::fs::write` followed it and wrote to its target. A render to a link
reported success while the target kept its old contents.

Unconfined writes go back to `std::fs::write`. Confined ones keep the staged
write, which is right there: `Roots::check` resolves the path first and has
already refused a link leading out of the root, so the write lands on the
resolved target inside it.

2026-10-19 00:52:40 +05:00

..

cli.rs

cli: an unconfined write still follows a symbolic link

2026-10-19 00:52:40 +05:00

export_depth.rs

Refuse incomplete SVG/PDF exports beyond the depth limit (#218)

2026-10-14 05:23:28 +07:00

fonts.rs

M7: list the fonts a file uses that aren't installed (#752)

2026-10-17 21:49:32 +07:00

pdf_print.rs

M6: PDF print options (bleed, marks, CMYK) (#92)

2026-10-10 20:50:29 +07:00

pdf.rs

M6: PDF export depth and REST conditional and variable-mode actions (#65)

2026-10-10 10:57:58 +07:00