fix: support microseconds and timezone offsets in timestamp ignore regex

[sohankshirsagar]

Summary

The built-in ignore_timestamps regex only matched ISO 8601 timestamps with exactly 3 fractional-second digits and an optional Z suffix. Timestamps with microsecond precision (6 digits) or numeric timezone offsets like +00:00 were not recognized, causing false deviations during drift runs.

Changes

• Updated the timestampRegex in dynamic_fields.go to accept any number of fractional-second digits (\.\d+ instead of \.\d{3}) and both Z and ±HH:MM timezone offsets ((Z|[+-]\d{2}:\d{2})? instead of Z?)
• Added test cases in dynamic_fields_test.go covering microseconds with +00:00, microseconds with Z, non-UTC offsets (+05:30, -04:00), and milliseconds with offsets

[tusk-dev]

Generated 8 tests - 8 passed

 

Tip

New to Tusk Unit Tests? Learn more here.

You are using "Only surface failing tests" mode, so Tusk will only surface failing tests in the PR comment but you can still see any passing tests in the Tusk UI.

Considered 8 test scenarios and 1 symbol in 1 file but found no failing tests.

View check history

Commit	Status	Output	Created (UTC)
d94e4e9	Generated 8 tests - 8 passed	Tests	Mar 19, 2026 8:22PM

Was Tusk helpful? Give feedback by reacting with 👍 or 👎

[cubic-dev-ai]

No issues found across 2 files