Was about to bump my local installation to pants2.22 …which led me to homebrew-tap pointing to scie-pants 0.12 …which seems to be pointing to pants2.21…looks like this individual opened a PR but the github-actions-workflows need to be approved. Can we bump

brew

to 2.22? Maybe for starters, approving those CICD pipelines so they can start testing?

Thanks Just checking that you're aware that ~any version of scie-pants can install ~any version of pants? The version referred to in the scie-pants repo is just used for building scie-pants itself. (It's a bit weird and recursive => scie-pants uses a specific version of pants to build, but the built scie-pants can run any version of pants)

(Not my PR) I’m managing pants via

brew

though; brew isn’t interpretting my pants.toml (that I know of..?)

(ah well... thanks for flagging it, anyway 🙂 )

Oh. I see. I tried changing my

pants.toml

and it fetched the latest pants. Neat 🙂

yay! yeah, it's a bit weird/confusing, but it's set up so that each person on a team only needs to install the scie-pants runner once(*) (via brew or otherwise) and then they automatically pick up new versions of the "real" pants code as

pants.toml

changes, without requiring any effort (* sometimes we make changes in newer versions of the real pants code that require newer scie-pants runners, but we try to have a warnings/deprecations guiding how to upgrade)