[jl-wynen]

Currently, running the script fails with

pixi run --script tools/collect-release-notes.py -- --cur-tag ${PACKAGE}/${VERSION} --compare-tag ${PACKAGE}/${LASTVERSION}

Error:   × no lock file exists for the script, but `--frozen` was requested
  help: Create one with `pixi lock --script <PATH>`.

(Reported by @nvaytet)

We would either need a lock file for the script (https://pixi.prefix.dev/latest/python/scripts/#lock-exact-versions) or allow resolving dependencies. This PR implements the latter.

Note that we need PIXI_NO_INSTALL: false in either case.

[nvaytet]

Can we add a bit more description here as to why we don't want lock files. Because someone later might just come along and think 'why not?' and just add them?

[nvaytet]

Why do we need this? It is not in the other files.

[jl-wynen]

Removed it

[nvaytet]

Don't we support windows?
Even if his is just for the CI builds, we have weekly builds on mac and windows?

[jl-wynen]

See the readme. I wanted to keep the lock files small. The weekly builds do not use any scripts as far as I can tell. Do you want me to add that anyway?

[nvaytet]

Not sure which readme you are refering to...
If the weekly builds don't use any scripts, do we need macos in there or can we make do with just linux?

All I'm saying is that as it looks now, the next person who will read this will wonder "did we forget windows? Or maybe we should remove macos?"

[jl-wynen]

I forgot to commit it and it's on my workstation... I'll add it when I'm back in the office.

All I'm saying is that as it looks now, the next person who will read this will wonder "did we forget windows? Or maybe we should remove macos?"

I added macos initially because some of us use it. Added windows now.

[nvaytet]

Is there a way we can test that this command actually works now?

[jl-wynen]

Not without running the workflow. Can we still run the workflow from the UI and have it run all steps except the actual upload?

[nvaytet]

Approval pending addition of the README file