Any sharp edges to watch out for when upgrading from 2.6 -> 2.8rc5? We want to test out the experimental bash target and golang support.

I'd recommend upgrading to 2.7.1 first so you can see any deprecation messages that apply to your codebase, and from there to 2.8.0rc5

Recently updated https://www.pantsbuild.org/v2.8/docs/upgrade-tips

side note here: i’m currently playing around with upgrading from 2.7.0 to 2.8.0rc5, and I’ve encountered a few import errors because of classes that got dropped and method names that got changed. I may have missed it, but i don’t recall seeing any deprecation warnings in 2.7.0 for example: •

pants.engine.process.InteractiveRunner

got dropped •

pants.core.target_types.FilesSources

got dropped and replaced with

FilesGeneratingSourcesField

•

pants.backend.python.target_types.PythonSources

got dropped and replaced with

PythonGeneratingSourcesBase

and

PythonSourceField

•

pants.build_graph.address.Address

had a

.maybe_convert_to_build_target()

method that got renamed to

.maybe_convert_to_generated_target()

did these changes not get deprecation notices or were they only added in 2.7.1?

Ah, sorry for that inconvenience! We don't consider the plugin API to be completely stable yet, so we don't do formal deprecations there yet.

good to know, thanks!

Sounds like this won't be helpful for you rn because you already fixed the issues, but we do have a plugin migration guide that I'll be updating today

@hundreds-father-404 that sounds great, lmk when that’s done so i can go over it to make sure i didn’t miss anything 🙂