As the previous comments suggest, there is a known bug within the minimize command for the given function. However, the result from the Optimization[Minimize] command is expected.
From the Optimization, Minimize help page: The Minimize command computes a LOCAL minimum of an objective function. In this case, Minimize finds a local minimum at: [-2.02634418581704, [x = .452809600260151]] and stops searching there.
If you tell Optimization[Minimize] to look at another specific interval, it will find the first local minimum and return that value (this was shown in my second example above).
The difference here is that the minimize command symbolically searches for a GLOBAL minmum, whereas the Optimization[Minimize] command returns the first LOCAL minimum it encounters within a certain range.