[temper] Configuration update#216
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Hygiene triageThis PR has been sitting since 2026-04-26. Two failures:
The config itself is sensible (weekly updates for github-actions + 5 cargo crates + 8 npm packages). Substantively merge-worthy. Suggested actions (your call):
Not closing unilaterally because this is a bot-managed PR and the policy implications are yours to set. |
There was a problem hiding this comment.
⚠️ Performance Alert ⚠️
Possible performance regression was detected for benchmark 'Rivet Criterion Benchmarks'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.20.
| Benchmark suite | Current: 6566c8b | Previous: 6dfdca6 | Ratio |
|---|---|---|---|
validate/10000 |
16134805 ns/iter (± 2176398) |
12167984 ns/iter (± 144437) |
1.33 |
This comment was automatically generated by workflow using github-action-benchmark.
Three queued feature requests now land: rivet bundle (#266), rivet coverage --matrix (#243), s-expr linked-via operator (#265). Plus externals load their own schemas (#267) and STPA TCL numbering is corrected to ISO 26262-8 (#257). Infrastructure: CI concurrency control across all workflows (#258), migration to self-hosted smithy runners (#262), release-npm trigger fix that retroactively unblocked v0.7.0/v0.8.0 npm publication (#261), weekly dependabot (#216), and the wasmtime 42→43 upgrade that retires the RUSTSEC-2026-0114 suppression introduced in v0.8.0 (#260). #125 (provenance-lifecycle) intentionally deferred — 5-week-old branch with conflicts in heavily-churned files (CLAUDE.md, ci.yml, settings). Needs its own attention session, not safe to autonomously rebase. Refs: FEAT-001 Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Automated configuration update from the Temper bot.
Review the changes and merge if they match the org standard.