Considering this breaks changing bids on 3.2, and 4.0 was only
released last week, this causes a serious problem for API users. The
90-day phase out implies that 3.2 will function as it had before
without changes. This is clearly not the case.
The proper way to do this would have been to release a 3.3 version
with getmincpc calls which would have returned $.10 until yahoo turned
on variable min bids. As it is right now, users must either live with
broken bidding or rush to test 4.0 and upgrade.
--- In email@example.com
, "jth_ewsapi" <justinh@...>
> 3.2.0 is not compatible with the new min bid scheme. You will need to
> upgrade to 4.0.
> --- In firstname.lastname@example.org, "Bryan" <bryanjj123@>
> > How does 3.2.0 deal with keywords which have min bids not equal to
> > $.10? I have received errors saying my new bids are too low, but there
> > is no way to check what the minimum bid is without upgrading to 4.0.