fix(vitest): report object retry options as a retry count

[gregberge]

Description

What

• buildTestMetadata() reports the configured retries as a number. Since Vitest 4.1 the retry option can be an object ({ count, delay, condition }): the metadata now takes its count, defaulting to 0 like Vitest's own runner (getRetryCount). A number is kept as is, and an unset retry is still left out.
• CurrentTask.retry in test-context.ts declares the object form, which number | undefined hid.
• Two tests in metadata.test.ts use real object options: { count: 2, delay: 0 } reports retries: 2, and { delay: 0 } reports 0.

Why

The task keeps the retry option as written, and buildTestMetadata() copied it into the metadata. On Vitest 5.0.2, it("probe", { retry: { count: 1, delay: 0 } }, …) gave retries: {"count":1,"delay":0}, while the metadata schema (packages/util/src/metadata.ts, mirrored in packages/api-client/src/schema.ts) expects number | null. Screenshots and snapshots both read this metadata, so every capture from such a test carried the invalid value.

Vitest sets task.retry to the test's own option or, failing that, the config's test.retry, so an object in the Vitest config would reach every test the same way. Taking only the count also keeps a condition function or RegExp out of the metadata, which crosses the browser/Node RPC boundary.

Type of changes

Bug fix (bug label).

Checklist

• I have read the CONTRIBUTING doc (there is no CONTRIBUTING doc in this repo)
• The commits message follows the Conventional Commits' policy
• Lint and unit tests pass locally
• I have added tests if needed

Optional checks:

• My changes requires a change to the documentation
• I have updated the documentation accordingly

Further comments

Testing

• vitest run --project unit in packages/vitest: 50 tests pass. The two new tests fail on the previous code, which returned { count: 2, delay: 0 } and { delay: 0 }.
• tsc and eslint . in packages/vitest, and Prettier on the changed files, pass.
• The branch starts from the commit before fix(vitest): make argosScreenshot and auto-naming work on Vitest 4.0 #390, which also edits metadata.ts and test-context.ts. It merges cleanly with current main, and the merged tree passes the unit tests (51 with fix(vitest): make argosScreenshot and auto-naming work on Vitest 4.0 #390's), tsc and eslint.
• The browser e2e project was not run: the value is normalized on the test side, before it crosses to Node.

For reviewers

• packages/core does not validate metadata before upload: readMetadata parses the JSON and updateBuild sends it unchanged. I couldn't check from this repo whether the API rejects an object retries. If it validates the request body, the whole updateBuild request would fail, not just one screenshot.
• The unit tests run only on the workspace's Vitest 5. The Vitest 4 compat jobs run the e2e project, so the new tests never run on 4.0, which has no object form.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
argos-js-sdk-reference	Ready	Preview	Oct 4, 2026 8:01am UTC