Skip to content

[temper] Configuration update#216

Merged
avrabe merged 2 commits into
mainfrom
bot/config-update-1777200301286
May 10, 2026
Merged

[temper] Configuration update#216
avrabe merged 2 commits into
mainfrom
bot/config-update-1777200301286

Conversation

@temper-pulseengine
Copy link
Copy Markdown
Contributor

Automated configuration update from the Temper bot.

Review the changes and merge if they match the org standard.

@temper-pulseengine temper-pulseengine Bot added automation Automation updates dependencies Dependency updates labels Apr 26, 2026
@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 26, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@avrabe
Copy link
Copy Markdown
Contributor

avrabe commented Apr 29, 2026

Hygiene triage

This PR has been sitting since 2026-04-26. Two failures:

  1. Playwright E2E — almost certainly an unrelated flake. A change to .github/dependabot.yml cannot affect frontend E2E tests. Re-running CI should clear it.

  2. .github/dependabot.yml validation (dependabot-api.githubapp.com) — this is dependabot's own config validation. Likely culprit: the YAML anchor + alias (labels: &ref_0 / labels: *ref_0) is technically valid YAML 1.2 but some dependabot validators choke on it. Replacing with explicit labels: [dependencies] blocks would resolve it.

The config itself is sensible (weekly updates for github-actions + 5 cargo crates + 8 npm packages). Substantively merge-worthy.

Suggested actions (your call):

  • Re-run CI to confirm Playwright is a flake, replace the YAML alias with explicit lists, and merge.
  • Or close this PR; the temper bot will likely re-propose with the same content next cycle, at which point the same fix applies.

Not closing unilaterally because this is a bot-managed PR and the policy implications are yours to set.

@avrabe avrabe merged commit 8dc93ca into main May 10, 2026
11 of 14 checks passed
@avrabe avrabe deleted the bot/config-update-1777200301286 branch May 10, 2026 18:54
Copy link
Copy Markdown

@github-actions github-actions Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ 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.

avrabe added a commit that referenced this pull request May 11, 2026
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automation Automation updates dependencies Dependency updates

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant