Version 18.0.0 -> 19.0.0

[philandstuff]

It's been a month, let's have a new release.

I plan to wait for #1065. All other current PRs are in draft, so I won't wait for them (but if they're finished quickly enough, that's fine).

[philandstuff]

I was wondering if #1073 really counts as a breaking change (I think it does but I wanted to check), and I got confused about this sentence in standard/versioning.md:

The contract for a "non-breaking" change is that any code that
parsed/resolved/type-checked/normalized successfully before must continue to do
so (modulo imported resources vanishing). The exception is the semantic
integrity check, which always changes with a new release of the standard.

This suggests that changing normalization behaviour isn't actually a breaking change (because it normalized successfully before, and it normalizes successfully after), but surely that can't be right?

Also I don't understand the second sentence - is it saying that every time we release a new version, the semantic integrity check changes? That doesn't sound right either.

[Gabriella439]

@philandstuff: Oh, that last sentence is incorrect and is a relic from back when the input to the semantic integrity check included the standard version. Nowadays, changes to normalization behavior are breaking changes