Worker routes in wrangler.toml not included in worker rollback?

Hi all, we had a scenario where we made a change to our worker routes in our wrangler.toml. We found that our worker had some issues serving the newly included routes, so we rolled back to the previous version. We assumed that the rollback would include reversion to the previous set of worker routes in the wrangler.toml, but found out that the worker routes were not changed by the rollback. Is this the intended behavior? That rollbacks only involve the worker code, and the wrangler.toml is excluded as that is a config for a separate deployment tool? Just looking for clarification so we know to stick to one toolchain for managing the versions if we need to.

To clarify, we used the Cloudflare deployments dashboard (not wrangler) to rollback.