Re-pin scriggo to the go-render index-truncation fix (#169)

Philipp Hossnerrequested to merge
fix/169-scriggo-repin into main

#169 (closed): re-pin scriggo to the go-render index-truncation fix

Re-pins the vendored scriggo render fork to the fix for #169 (closed) — the int8(len(Functions)) → uint8 function-index truncation that silently rendered the wrong sub-function once a single compiled function referenced more than 256 go-render targets (full-length output, no error). Fork MR !130 (merged) (merged non-squash) routes the index through the existing bounded guard for both the parallel-render (OpGoRender) and regular-call paths, turning the silent wrap into a build-time limit error; it also swept the identical latent bug in predefFunc.

  • go.mod: gitlab.com/haproxy-haptic/scriggo → v0.0.0-20260822205936-3991b6164fc0 (the fix commit, now on fork main).
  • pkg/templating/gorender_limit_test.go: a HAPTIC-side regression test rendering >256 distinct {{ go render … }} sites in one function and asserting a build-time limit error surfaces (not silent wrong output) — proving the guard reaches HAPTIC through AllowGoStmt: false (which doesn't gate the expression-form parallel render).
  • CHANGELOG: [Unreleased] Fixed entry.

The bundled chart never hits the limit (one macro reused in a runtime loop = one index), so this is a latent-correctness fix; the regression test locks it. make test + make lint green.

Merge request reports