Potential issue with pallet versions using `pop new parachain`

[tsenovilla]

Hey,

I was addressing some comments from @AlexD10S in #524 and realized there might be a subtle bug with pop new parachain. Anyway I'm sharing it as I'm sure you'll find it interesting.

Imagine I run pop new parachain my_parachain --release-tag polkadot-stable2412 and suppose I wanna add pallet-contracts to my template. I'd expect that adding

pallet-contracts = { git = "https://github.com/paritytech/polkadot-sdk", branch = "stable2412", default-features = false }

to my Cargo.toml compiles, as it's pointing to the same release I used to generate the template. However there's a dependencies conflict here :(

After a quick review I noticed that the issue is the version used by cumulus-client-consensus-aura. It should be 0.21.0, accordingly to the stable2412 branch of the sdk, but it's 0.20.0 in the template.

A quick workaround I came across with is to update the template to use git branches instead of concrete versions in the Cargo.toml, that way you'll be always up to date with the last version of crates pushed to a stable version of the sdk, but maybe there's a better approach.

Hope this will be helpful to continue improving POP 🚀🚀