May be a bit more than I expected: My thinking is that the developer should accept the responsibility of ensuring that:
The distribution channel has all info necessary for deciding what versions of the support software it works with, including modifying the statement as required over time to indicate whether newer versions than it was originally released for are supported.
All necessary information for installing the software is clear and complete, including reacting with improvements to complaints that it is not.
A clear statement of the bug fix and improvement policy.
Remove the software from the distribution channel when it is overtaken by time and events. Dumping on the channel and forgetting it is not very polite nor responsible over the long run.
So IMHO a developer should assume the on-going responsibility to keep the “point-of-sale” decision-making information up to date with the changing environment. For support of the actual application itself there should probably be a different standard for open-source vs no-source. For open source a “here it is - it’s all yours now” is probably acceptable if not exactly desirable, but w/o source an approach similar to what you describe is probably the minimum as long as your decisions about your obligation are driven by some concept of fairness and the greater good for the most users and not just how bad your hangover is.