https://www.sqlite.org/formatchng.html

comes up when I search for 'file format changes' but does not include the changes which would concern most SQLite users. It stops at version 3.0.0. Since almost all of the documentation concerns SQLite3, I feel it should start at version 3.0.0, and mention

• WITHOUT ROWID, version 3.8.2 (2013-12-06)
• indexes on expressions, version 3.9.0 (2015-10-14)
• GENERATED columns, version 3.31.0 (2020-01-22)
• STRICT tables, version 3.37.0 (2021-11-27)

and probably others that don't come to mind. Can anyone think of ones I missed ?

It can also explain how backwards-compatible each change is (or have just one section if they're all the same).

If the team doesn't want to work on an up-to-date version of the page, could it at least remove the existing one, so that people looking for help with SQLite get the individual pages and not a red herring about an obsolete version ?

But those are NOT format changes, but new SQL capabilities.

Stricto sensu, the file format itself didn't change.

Mmm. Right. Yeah. They are not format changes. They are introductions which stop SQLite being backward-compatible. Or something like that.

I take your point. But I do feel that it would be useful to document these all on one page, which can be found by anyone using websearch to look for that problem. But now I don't have a good title for the page.

It's all be documented actually.

Of course. And it's also in https://www.sqlite.org/changes.html.

will be more convenient ... a summary page

Indeed. A page that focuses on forward-compatibility would be very much welcome.

I.e. a page listing new SQL features/syntax (and related dates and versions, linking to the changes page), that older SQLite versions choke on.

Note that above I wrote forward-compatibility, but I'm not sure it's the correct terms.
I consider backward-compatibility as the ability of newer versions of SQLite to open older DB files.
So that's not it here, which is about older versions of SQLite breaking down (i.e. not understanding)
the SQL used in DB files created using newer versions of SQLite. Is that forward-compatibility?

Note that above I wrote forward-compatibility, but I'm not sure it's the correct terms. I consider backward-compatibility as the ability of newer versions of SQLite to open older DB files.

FWIW, that matches with https://sqlite.org/formatchng.html, where the terms "forward compatible" and "backwards compatible" are specifically defined.

So that's not it here, which is about older versions of SQLite breaking down (i.e. not understanding) the SQL used in DB files created using newer versions of SQLite. Is that forward-compatibility?

According to formatchng.html, yes.