[dependabot]

Bumps arktype from 2.2.8 to 2.2.9.

Changelog

Sourced from arktype's changelog.

2.2.9

Keep tuple elements around defaults in .in and .out

Combining a tuple's defaultable elements with its other elements dropped some of them, depending on key order:

const T = type(["string", "number = 5", "boolean?"])
// was: [string, boolean?]
// now: [string, number?, boolean?]
T.in.expression
// was: number[]
// now: [number, string, ...number[]]
type(["number", "string = 'foo'", "...", "number[]"]).out.expression

A bound that narrows two existing length constraints at once also no longer throws "multiple distinct intersection results":

// was: throws
// now: string == 2
type("1 <= string <= 2").and("string >= 2")

Thanks to @​ybai08 (#1696).

Reject NaN in unions discriminated by typeof

number rejects NaN, but compiled unions like number | null dropped that check when they discriminated by typeof, so NaN was only rejected with jitless (#1702).

const T = type("number | null")
// was: NaN
// now: ArkErrors: must be a number (was NaN)
T(NaN)

Thanks to @​thecotne.

Don't treat Object.prototype keys as declared

Inherited names like toString or constructor, and an own __proto__ key like the one JSON.parse creates, were treated as declared keys, so "+": "delete" kept them and "+": "reject" accepted them (#1701).

const T = type({ a: "string", "+": "reject" })
// was: { a: "x", constructor: 1 }
</tr></table>

... (truncated)

Commits

• cfded1a release: arktype 2.2.9 + dependents (#1704)
• 092075a fix(schema): keep tuple elements around defaults in .in and .out (#1696)
• fc06904 fix(schema): only emit referenced $defs in toJsonSchema (#1689)
• cd11e1f fix(schema): don't treat Object.prototype keys as declared for undeclared key...
• c82c596 fix(schema): keep the NaN check when a union discriminates on typeof (#1702)
• 5aad144 fix(schema): convert what JSON Schema can't represent in ~standard.jsonSchema...
• 9d60ec7 docs: simpler landing examples, Markdown docs for agents, and an ArkType skil...
• See full diff in compare view

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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/openworkflowdev/openworkflow/@openworkflow/cli@932

npm i https://pkg.pr.new/openworkflowdev/openworkflow/@openworkflow/dashboard@932

npm i https://pkg.pr.new/openworkflowdev/openworkflow@932

commit: 4cc1566