It's critical for us because the Scalameta version...
# development
l
It's critical for us because the Scalameta version in the current stable version of Pants simply can't parse our code as it uses Scala 3.3.0 syntax that isn't supported in that version
w
I don’t know the state of the PR (if it’s been PR’d and accepted or not), but could something like this be useful to you in the meantime? https://www.pantsbuild.org/docs/manual-installation#running-pants-from-unreleased-builds
f
The PR has been merged. It needs to be "cherry-picked" back to the 2,17.x branch (and potentially the 2.16.x branch). The next release of those branches will contain it.
@wide-midnight-78598: Are those docs out of date because they still refer to
./pants
and not the scie-pants launcher?
w
Doh, I think they are.. I believe scie pants allows installing from SHA
l
Cool, thanks @fast-nail-55400
f
There is automation to make the cherry-pick PRs, but I need to figure out how to trigger the automation with the PR closed (since it usually triggers when the label exists at merge time).
So I would rely on the "Pants from main branch" functionality which @wide-midnight-78598 mentioned until the commit is cherry picked and a release also occurs.
l
Sounds good
f
h
@loud-lizard-27679 which pants version are you currently on?
I'll be sure to merge this into 2.17.x before the next (and ideally final) release candidate
❤️ 1
which should be in the next day or so
l
@happy-kitchen-89482 We're not using Pants productively yet, we're evaluating
I was doing my evaluation using 2.16.0 as that is the latest stable version
h
Ah OK, cool
so switching to 2.17 wouldn't be too much of a hassle?
l
No
But 2.17 isn't released yet right?
h
I'm releasing its hopefully final release candidate as we speak
l
Cool, can I put RC versions in pants.toml?
f
I did back port the change to 2.16.x as well.
l
Yeah, by the time we use this productively 2.17 is probably going to be done
h
Yes, you can plug any dev or rc version in pants.toml
l
That makes my life easy 🥰