Skip to main content

Update your development environment

You must update your development environment when there is a new release of the Intrinsic platform and associated SDK.

info

If you followed the guide in Set up your development environment and selected "latest" as the tag for your development container image, VSCode will always pull the latest available image as needed.

If you have selected a specific version in your devcontainer.json file, then VSCode will notify you if newer versions are available and prompt you to update the configuration accordingly.

To update your development environment to a specific version, do the following:

Determine the version to update to​

Your development environment should match the version of your solution. To determine the version of your solution:

  1. Start your solution using Intrinsic Flowstate.

  2. After your solution has been deployed, view the solution details.
    The version displayed will look similar to this: intrinsic.platform.20250414.RC03.
    Notice that it contains a date.

    Solution version

  3. Find a tag that starts with v and contains the same date in the list of releases on the SDK repository. For example, the version intrinsic.platform.20250414.RC03 matches the release v1.18.20250414.
    Remember this release for the next steps.

Update the Dev Container version​

  1. Open your .devcontainer/devcontainer.json file.

  2. Change the value of image to ghcr.io/intrinsic-ai/intrinsic-dev-img:TAG where TAG is the tag from the previous step. For example, the tag v1.18.20250414 corresponds to the image ghcr.io/intrinsic-ai/intrinsic-dev-img:1.18.20250414. Note that devcontainer images do not have a v in the version number while SDK versions contain a v.
    You can check all available Dev Container tags by visiting the GitHub package page

  3. Save and close .devcontainer/devcontainer.json.

  4. Close Visual Studio Code and reopen it.

  5. Press Ctrl+Shift+P and select the option Dev Containers: Rebuild Container Without Cache. This will update your Dev Container version. In case this does not succeed to update your Dev Container version, you should close Visual Studio Code and reopen it. Then try again.

info

In a Dev Container, you can always check the current version by running inctl version in the VSCode command line.

Next, update your SDK version.

Update the SDK version​

danger

inctl bazel init modifies files in your bazel workspace. Make sure all code is backed up before following these instructions.

The version of the SDK you use should match your Dev Container version. Use the same TAG that you used in the previous section.

  1. Open a terminal in Visual Studio Code.

  2. Backup all files in your workspace, especially the files .bazelrc and MODULE.bazel. For example, you could backup your files using git commit.

  3. Use inctl bazel init to overwrite bazel related files in your workspace. Make sure to replace TAG with the tag chosen earlier (ex: v1.18.20250414).

    inctl bazel init --sdk_repository=https://github.com/intrinsic-ai/sdk.git --sdk_version TAG --override
    note

    You can always see the currently configured SDK version when you open the MODULE.bazel file and look at the URL specified for bazel_dep(name = "ai_intrinsic_sdks").

  4. If you made changes to your previous .bazelrc file, then compare the new .bazelrc file to your previous .bazelrc file. Migrate any customizations you made into the new .bazelrc file.

    note

    Only migrate changes from your previous .bazelrc file that were intentionally added by you.

    note

    If the version you're upgrading to is v1.11 or higher, then make sure your .bazelrc does not contain --enable_bzlmod=false.

  5. If you added additional dependencies to your previous MODULE.bazel file, then compare the new MODULE.bazel file to your previous MODULE.bazel file. Migrate any additional dependencies to your new MODULE.bazel file.

    note

    Only migrate dependencies that were intentionally added to your previous MODULE.bazel file.

Your development environment is now fully up to date!

Troubleshoot updates​

If you have problems after an update, see these troubleshooting steps.