pixi build pixi.lock doesn't include proper version

[pavelzw]

Checks

• I have checked that this issue has not already been reported.

• I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example

Quantco/polarify#81

# pixi.toml
[project]
name = "polarify"
# <version not set here>
# ...
[package]
version = "0.2.0"
# ...

Issue description

pixi.lock looks like this:

- conda: .
  name: polarify
  version: 0.1.0
  build: pyhbf21a9e_0
  subdir: noarch
  depends:
  - python
  input:
    hash: 4f79b562092ea284f5aee2a320868102e5a32984839c350c8f78170339fe2516
    globs:
    - pixi.toml

Expected behavior

pixi.lock should look like this:

- conda: .
  name: polarify
  version: 0.2.0
  build: pyhbf21a9e_0
  subdir: noarch
  depends:
  - python
  input:
    hash: 4f79b562092ea284f5aee2a320868102e5a32984839c350c8f78170339fe2516
    globs:
    - pixi.toml

[pavelzw]

when i set my project.version to 0.2.0 (before, it was unset), it works.
what is package.version supposed to be used for?

[wolfv]

This would fix the issue about taking the version from [package]: prefix-dev/pixi-build-backends#21 (assuming you use the python build backend).

[wolfv]

Should be fixed with the latest build backend release. Note that you currentyl have to clean it manually, locally, in the cache dir, e.g. something like rm -rf /Users/wolfv/Library/Caches/rattler/cache/cached-build-envs-v0/