Skip to content

chore(hub): migrate samod to shikokuchuo/samod@access-policy (automerge 0.10)#355

Draft
shikokuchuo wants to merge 1 commit into
mainfrom
feature/bd-qp353u2b-migrate-samod-access-policy
Draft

chore(hub): migrate samod to shikokuchuo/samod@access-policy (automerge 0.10)#355
shikokuchuo wants to merge 1 commit into
mainfrom
feature/bd-qp353u2b-migrate-samod-access-policy

Conversation

@shikokuchuo

@shikokuchuo shikokuchuo commented Jul 1, 2026

Copy link
Copy Markdown
Member
  • Migrates the vendored samod fork from quarto-dev/samod@q2 (samod 0.9 / automerge 0.8) to shikokuchuo/samod@access-policy (samod 0.12.1 / automerge 0.10) in quarto-hub and quarto-preview.
  • Ports AuditAccessPolicy to the new synchronous AccessPolicy trait (is_allowed).
  • No automerge 0.8→0.10 source breaks surfaced; JS↔Rust wire + on-disk formats verified compatible.

Tracked as braid bd-qp353u2b.

…ge 0.10)

Switch the vendored samod fork from quarto-dev@q2 (samod 0.9.0 / automerge
0.8.0) to shikokuchuo@access-policy (samod 0.12.1 / automerge 0.10.0) in
quarto-hub and quarto-preview. AccessPolicy is now synchronous (should_allow →
is_allowed, borrowed args, bool return); AuditAccessPolicy ported mechanically
and its "Document accessed" audit log now has a tracing-capture regression test.
No automerge 0.8→0.10 source breaks surfaced; single unified automerge 0.10 in
the lockfile. bd-qp353u2b.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant