I'm seeing resolving behaviour in Tridion 2013 SP1 that's quite different than what I was used to seeing in 2011 SP1...
On one implementation, in 2011 SP1 I had a case where there were a bunch of interlinked components. e.g. a promo component would link to an article, the article would be linked to from other components. So this caused the usual avalanche of publish items. I fixed that with a custom resolver by filtering out the unneeded items.
On another implementation, in 2013 SP1 we have an article component and a container component that holds articles. I was expecting that if I publish an article, the containers that use this article would get published to, but no. All I see in the "Items to Publish" list is the component itself.
So my theory is that at some point after 2011 sp1, the resolver logic was changed to not have the avalanche by default, rather the other way around. Can anyone confirm/deny this?