Version 1.2.1

[sinclairzx81]

This PR fixes a regex escaping bug in NumberPattern that allowed non-numeric characters through.

Issue

The issue appears localized to types of TRecord<TNumber, TSchema> and TemplateLiteral<[TNumber, ...]>, both of which use the NumberPattern to encode patterned expressions. All other patterns appear ok.

Additional

This issue was reported publicly via Reddit post using an LLM to audit. Output copy below.

const R = Type.Record(Type.Number(), Type.String())
Object.keys(R.patternProperties)[0]   // '^-?(?:0|[1-9][0-9]*)(?:.[0-9]+)?$'
//                                                   unescaped ----^
Check(R, { '1x5': 42 })   // false — '1x5' classified as a NUMERIC key ('x' matches the dot)
const data = { '1x5': 42 }
const r: Static<typeof R> = data   // ✓ compiles — TS: '1x5' isn't a numeric key, unconstrained

Updates

The decimal separator . was unescaped, causing it to match any character rather than a literal dot. For example, 1x5 would incorrectly pass as a valid number.

// Before
export const NumberPattern = '-?(?:0|[1-9][0-9]*)(?:\.[0-9]+)?'

// After
export const NumberPattern = '-?(?:0|[1-9][0-9]*)(?:\\.[0-9]+)?'

Additional

This PR has an additional upstream fix to handle double-backslash escaping in ParseBox's parser generator.

sinclairzx81/parsebox#16