SDK out of sync while using latest version

I'm unclear why nRF Connect warns me that my SDK is out of sync even though I'm using the latest version. In fact, the latest SDK version is the only one installed, which was done by nRF Connect itself.


VS Code notification for out of sync SDK

Is this simply informing me that I'm behind certain repos because I'm not using a West Workspace? Is this an inevitable consequence of using stand-alone application directories and relying on nRF Connect to find the globally installed SDK?

More importantly, will I still be on version 2.5.1 if I accept the suggestion to run "west update", or will this modify my installed SDK to the main 2.5.99 development branch?

Parents
  • I'm obviously the only idiot who doesn't understand this, because I haven't found one single similar question here on DevZone.

    I would understand being out of sync if I were using a development branch (e.g. v2.5.99), as those repos are in constant flux, but I thought the entire point of tagged releases is that they are fixed. Doesn't the West manifest reference a list of exacting versions verified to work together?

    Am I simply mistaken in my assumption that the tagged releases are unchanging? Or do I perhaps have a configuration error?

    Any wisdom someone can provide is much appreciated.

Reply
  • I'm obviously the only idiot who doesn't understand this, because I haven't found one single similar question here on DevZone.

    I would understand being out of sync if I were using a development branch (e.g. v2.5.99), as those repos are in constant flux, but I thought the entire point of tagged releases is that they are fixed. Doesn't the West manifest reference a list of exacting versions verified to work together?

    Am I simply mistaken in my assumption that the tagged releases are unchanging? Or do I perhaps have a configuration error?

    Any wisdom someone can provide is much appreciated.

Children
Related