Validity of DateTime from setZone with a valid Zone

[MartinP-C]

I incorrectly raised an issue about the TS types for Luxon: #1739

Before I head off to DefinitelyTyped..
Can I confirm that calling setZone with a valid Zone should definitely produce a valid DateTime?
Assuming the DateTime is valid to begin with?

ie.

const validDateTime = DateTime.now(); // now is always valid
const maybeValidZone = IANAZone.create(userInput);

if (maybeValidZone.isValid) {
  const zonedDateTime = validDateTime.setZone(maybeValidZone); // maybeValidZone is valid as passed check;
  // therefore is zoneDateTime guranteed to be valid?
}

[diesieben07]

The correct answer is: No.
However this can only happen in the edge case where the zone conversion causes Luxon to have to create an invalid Date (see: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date#the_epoch_timestamps_and_invalid_date).
Let me demonstrate:

// the following date is valid, but it is the maximum Date
const date = DateTime.fromMillis(8640000000000000, { zone: "UTC" });
// this zone is valid
const zone = IANAZone.create("Europe/Berlin");
// this date is invalid, because adding the zone offset pushes it over the "maximum date" 
const zonedDate = date.setZone(zone);

[MartinP-C]

Oh man. Hadn't even considered that!
Aren't dates fun