Released: Jul 1, 2026

Updates in 2026.1 Build 236396

Fixes

• Updated Performance Monitor plugin UI to match Ring UI design system.
• Projects import: preserve ids on importing to empty server, making it clear that ids are changing when they do.
• Show the Performance Monitor tab for jobs.
• "Unmet requirements: exists:" for incompatible agents instead of clear description.
• Horizontal sidebar behaviour is unclear and unstable.
• NPM integration has unnecessary text and jumps.
• Build features UI: placeholder in the search field refers to non-existing items.
• Pipeline YAML Editor: incorrect error count + misaligned error view.
• Edit Repository: CSP and PR toggles are available for Any Git Repo with auth type - Anonymous.
• Pipeline integrations: bring the "Test connection" back.
• Pipeline yaml parse error should contain location in the yaml.
• Agent Requirement: RAM Amount condition doesn't work.
• Adding tags to a pipeline leads to "Error while loading data", the pipeline is inaccessible.
• Edit Repository: Missing CSP status in the repository component description.
• Pipeline is broken after project copying.
• An empty Repository entity is created if the user switches from the pipeline setting to the Admin area.
• Highlight repository names by exact match, not by symbols.
• Pipeline steps description isn't aligned with steps if docker file is used in some of the steps.
• Do not show the text about DSL inconsistency from the DSL tab of pipelines stored in YAML.
• POM location is in the Advanced Maven settings for pipelines.
• Cannot create Pipeline, if there is a Build configuration with the same name on the same project level.
• Broken build if reusing a pipeline with failed jobs in a build chain.
• Show all inherited pipeline parameters by default.
• Limit Job Id and Job name length.
• Perforce failing on newlines in changelist description.
• Do not shutdown docker compose right on build interruption, as it prevents 'always running' steps from proper execution.
• Stop build command from the server may cancel the step set to be always executed.
• Allow Run Custom Build dialog to be resized (to show long values in drop-downs).
• Build cannot resolve dep. parameters, if it has optional artifact dependency on another skipped conditional dependency.
• No "Log in" next to the newly created connection in the dropdown.
• AWS SDK2: remove "(SDK Attempt Count: 1)" from the errors, return back the error code and service name.
• CONNECT: 401 on access to K8s via proxy with login and password.
• Creation flow: repository description is always absent for the connections.
• No reaction after activation of the security patch (it is unclear whether the installation has actually started).
• 'Store password and API tokens outside of VCS' gets hidden when you disable UI-managed project settings.
• Using the Filter button on Change Log tab of Versioned Settings leads to 403 CRSF error.
• Perforce shelve trigger starts a build on excluded stream if feature branches support is disabled.
• VCS trigger doesn't trigger build on empty branch.
• Free Disk Space should be able to delete volumes of docker builder.
• Failed DSL compilation due to invalid cache after moving a Perforce label.
• Failed to resolve artifact dependency in multinode setup with external artifact storage.
• 'All compatible agents are outdated and cannot be upgraded' is shown even though some agents are currently undergoing the upgrade process.
• Deadlock on attempt to save data to test_metadata table.
• Artifact is missing from the TeamCity web UI while existing in the external storage.
• TCP Run in Docker: Docker Image autocomplete prioritizes loose substring matches over prefix.
• The Add Step dialog is not switched automatically to "All" when searching.
• "Force virtual host addressing" checkbox doesn't work.
• Cloud Image can't be moved to a pool not containing the project that contains this image.
• Dorm: Canceled build without agent cannot be displayed: "You do not have enough permissions to view requested agent pool".
• .NET builds with qualifier agent requirements starting with "Exists=>" cannot find compatible agents if there are incompatible agents in the same pool.
• Lots of duplicate entry errors on attempt to store a metric id to the dictionary table.
• Perforce failing on newlines in changelist description.
• Agent alternate IP address ignored by TeamCity.
• Working better with non-default branches using MCP.
• Cleanup of build type groups can fail with an unknown error.
• Rake build steps are broken (plugin is damaged).
• Authorize virtual agents action should validate agent pool for cloud agents.
• [S3] Uploads fail with 403 status code.
• Build-scoped tokens UX: add descriptions and docs link.
• Properties for key preserving on rotation (time.min and time.days) are not working.
• TeamCity cleanup does not remove cancelled multi-node tasks.
• Creation flow: handle Unauthorized exception in the UI.
• Excessive '/user' calls during repository listing in BitBucket Cloud connection.
• Provide more information about the origin of the TeamCity server workspaces.
• IndexOutOfBoundsException in org.jetbrains.teamcity.fus.client.events.TeamCityListener.
• Mark test ignored if it was interrupted and parent block gets closed.
• Messages "Agent will upgrade" and "Agent can't be upgraded automatically" can be shown at the same time.
• Incorrect "mcpClientToolName" sent to FUS during connection to MCP with Gemini, Copilot and some other tools.
• Project import loads the whole custom_data_body table.
• Saving settings on Windows can be slow.
• Repeating changes collection operations holds a reference to a previous operation via '$0'.
• Add a primary key to the ignored_tests table to help improve performance of DB replication.
• BuildPTRIndexer$BuildTask.beforeExecute consumes CPU in case of a large queue.
• PageExtensionsInterceptor is called for non-WEB POST requests.
• Calculation of unprocessed node events takes a lot of time.
• Processing of the events blocks on VCS commits cache initialization.
• Slow loading of VCS leads to UI slowness.
• Server cleanup duration ~3x regression on SQL Server after 2025.11.3 upgrade.
• Too big thread name with lots of "commit" strings.
• Duplicated IDs in the where clause of the SQL query can cause the PostgreSQL planner to switch to a full table scan.
• Avoid loading the entire VCS root DAG of commits in memory.