Is there a way to go back to the old way Pants generated the command at the top of the lockfile header? Some versions ago it was relative e.g.

./pants generate-lockfiles --resolve=my-resolve

. Recently it's become an absolute path which is quite annoying.

That seems inadvertent. I don’t recall any decision to do so, and it wouldn’t make sense. Can you file a bug?

any change in how you invoked pants when you generated the lockfile?

Thank you @curved-television-6568! That pointed me in the right direction. This seems to be due to the type of shell one is using. Bash indeed sets

PANTS_BIN_NAME

to the value actually invoked, in our case

./pants

. Other shells, like fish (the one I'm using), converts this to an absolute path e.g.,

/home/johan/project/pants

. In short, this is no fault of pants and it looks like we need to work around this in another way :)