Coverage remained the same at 86.573% when pulling 0a77ebb on C-l-o-u-d:patch-1 into 91efde6 on gajus:master.

This will obviously break other timestamps.

There needs to be a test case for both timestamp variations.

this only applies to type name: 'timestamptz',

const timestampParser = (value: string | null) => {
   return value === null ? value : Date.parse(value);
   return value === null ? value : Date.parse(value + ' UTC');
 };

 export const createTimestampWithTimeZoneTypeParser = (): TypeParserType => {
  return {
    name: 'timestamptz',
    parse: timestampParser,
  };
};

others has different type name: 'timestamp',

And NicolasCaous also wrote about it in the original issue: #239 (comment) in the 'Possible Solution' section that However, timestamptz works flawlessly. (it was before this commit 1e9a484)

Thank you

🎉 This PR is included in version 24.1.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀