Assembly Versioning
Documentation menu
Assembly versions and package versions answer different questions. Keep both intentional so a runtime error report and a package listing agree on what was shipped.
Package version
The package version is what a consumer sees and what dependency ranges refer to. It should follow semantic versioning and match the release notes.
Assembly version
The assembly version is part of the assembly identity. Changing it can affect binding on .NET Framework. Many libraries keep the assembly version stable across compatible releases and let the package version carry the release number.
Automation
The templates can derive the package version from a changelog and tag the commit. Whatever scheme you choose, write it down and make the pipeline the only place that applies it.