The CHF1 for CF 9.0.1 is such an example (there are others). Note that its steps 6-9 involve updating files in WEB-INF/cftags and CFIDE directories.
In such a case, we simply just can’t expect that the next CHF will somehow apply those updates, if that next CHF is another instance of the simple kind that involves just updating a single jar. I hope you can see that this isn’t something where we can “blame” Adobe for “causing this problem” of having to do such manual steps from an earlier CHF.
That said, I suppose we could argue that if any subsequent CHF has previous ones that had manual steps, that CHF could make it clear to readers. (Then I wouldn’t have had to write this blog entry and offer the table below. BTW, you may note that I could add comments to the technotes, and I have indeed done that on some.)
Until and unless Adobe implements a more automated system for applying updates (and I really don’t want to debate that, as it’s just not my focus here), then it just “is what it is”, that you simply NEED to look at any prior CHFs that you may be trying to “skip” in getting up-to-date.
Wow. Thanks Charlie for putting this together as I am sure this is rampant in the wild.