Bump vite from 5.4.19 to 5.4.20 - #1
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 5.4.19 to 5.4.20. - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/v5.4.20/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/v5.4.20/packages/vite) --- updated-dependencies: - dependency-name: vite dependency-version: 5.4.20 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Author
|
Superseded by #3. |
sirwolfgang
pushed a commit
that referenced
this pull request
Sep 29, 2026
A scenario suite replays every selected prompt through the agent once per model, so creating a suite that runs, or running one, is agent execution. EvaluationsController now applies the gates AgentsController#execute does — the dashboard's execution switch, the owner's execution quota, and no observed (read-only) agents — and ScenarioEvaluationRunner reports each replay to the host as one execution, so a read-only dashboard stays read-only and a metered host meters suites. Evaluation core: - Runner: an exception inside the replay callable is an errored Replay again (an ArgumentError from a provider aborted the whole run); only a return value that is neither a Replay nor a Hash raises. - Scorer: a pattern matches as a substring before it is tried as a regex, so `$5` or `1,060 (locally)` mean what they say, and regexes compile with a timeout so a pathological pattern cannot stall the job. - Diagnosis: "I can't find any…" and "I don't see…" report a negative result, not a missing capability. - Report: a model with no cost estimate ranks after one with a known cost in the verdict tie-break (unknown sorted as free); a prompt containing "|" no longer breaks the markdown matrix. - ScenarioParser: a backticked span is the prompt only when it opens the line; `#1 priority…` is not a heading; the colon-heading rule skips questions and optioned lines and is documented; a repeated named key is reassigned instead of merging two scenarios; a single JSON object and an `expect:` sub-hash are accepted. - Judge: a suggested tool that is not `{ name, description }` is normalised or dropped rather than rendered as an empty tool. Dashboard: - Evaluation#run! hands a pre-created run to the scenario runner even when the suite has since lost its scenarios, so it fails instead of staying pending; replace_scenarios! keeps a surviving scenario's enabled flag; scenario_groups reads the preloaded association on the index. - ScenarioSuitePanel keeps polling after a failed fetch, keeps every scenario in the matrix after a partial run, exports notes when editing, and takes its columns from the selection while a run is in progress. Docs: the judge example and instructions in evaluations.md run as written, `on_result:` belongs to Runner.new, the install docs name the third migration, and the CHANGELOG covers ActionAgent.mcp_catalog. The json pin comment no longer claims JSON.generate changed. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GeDtAWaXoeNCB6RNxg8m8r
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps vite from 5.4.19 to 5.4.20.
Release notes
Sourced from vite's releases.
Changelog
Sourced from vite's changelog.
Commits
997700frelease: v5.4.20482000ffix: applyfs.strictcheck to HTML files (#20736)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.