TeamCity On-Premises 2026.1.1

Released: May 29, 2026

Atualizações na 2026.1.1

Correções

  • 'Force virtual host addressing' checkbox doesn't work.
  • .NET builds with qualifier agent requirements starting with "Exists" cannot find compatible agents if there are incompatible agents in the same pool.
  • Perforce failing on newlines in changelist description.
  • Agent alternate IP address ignored by TeamCity.
  • Working better with non-default branches using MCP.
  • 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 line.
  • 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.
  • 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.
  • No reaction after activation of the security patch (it is unclear whether the installation has actually started).
  • Build cannot resolve dep. parameters, if it has an optional artifact dependency on another skipped conditional dependency.
  • 'Store password and API tokens outside of VCS' gets hidden when you disable UI-managed project settings.
  • Perforce shelve trigger starts a build on excluded stream if feature branches support is disabled.
  • VCS trigger doesn't trigger build on empty branch.
  • Failed DSL compilation due to invalid cache after moving a Perforce label.
  • Failed to resolve artifact dependency in multinode setup with external artifact storage.
  • Build features UI: placeholder in the search field refers to non-existing items.
  • '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.
  • Excessive /user calls during repository listing in BitBucket Cloud connection.
  • Pipeline is broken after project copying.
  • Pipeline steps description is not aligned with steps if Dockerfile is used in some of these steps.
  • /app/pipeline MCP requests do not work when user has active 2FA.
  • Limit Job ID and name lengths.
  • Pipeline YAML parse error should contain location in the YAML.
  • RAM Amount condition for pipeline agent requirements doesn't work.
  • 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.
  • Saving settings on Windows can be slow.
  • Repeating changes collection operations holds a reference to a previous operation via 'this$0'.
  • PageExtensionsInterceptor is called for non-WEB POST requests.
  • Slow loading of VCS leads to UI slow down.