I just want to clarify something. Depending on which config you based your own, you will get a different behaviour.
tk-config-basic based configs will get the latest version of a config every single time you launch a DCC.
tk-config-default2 based configs on the other hand will get the latest version of a config when you launch a project from Shotgun Desktop and not every single time you launch a DCC.
It all boils down to a pretty cryptic setting in an engine’s config named
launch_builtin_plugins (see here in the basic config). When this setting is set to
[basic] on a engine for a given environment (project in this case), the Toolkit will use our newer startup logic which will download the latest version of a pipeline configuration from Shotgun instead of using the one that was downloaded by the Shotgun Desktop.
It’s a bit of oversight on our part, this setting should have been present in the
default2 config and we’re considering making this behaviour the default one regardless of this setting’s value, but doing so might mean we would have deprecate older versions of tk-core which we always careful about doing so we want to think this through first.