Bitbucket Cloud will permanently remove app password authentication on July 28

Bitbucket Cloud is running controlled brownouts from June 9 to July 27, 2026, after which app passwords will be permanently removed on July 28, 2026. All CI/CD pipelines, scripts, and integrations that authenticate via app passwords must migrate to scoped API tokens before the deadline. This is a hard breaking change: any Veeam backup connector or restore automation using app password credentials against Bitbucket Cloud will stop working after July 28.

GitHub Copilot for Jira reached GA on or around June 27, 2026, building on its March 2026 public preview. It now supports real-time agent progress streaming directly into Jira tickets, follow-up instructions in the Jira chat panel, Confluence context via MCP, and custom agents. This tightens the GitHub–Atlassian integration loop, creating a new agentic surface in Jira that Veeam should monitor for data residency implications, as agent sessions may process issue content, acceptance criteria, and linked repo data.

Released June 26, 2026, GitHub Desktop 3.6 embeds Copilot into commit message authoring, merge conflict resolution, and Git worktree support. Copilot now runs on the shared Copilot SDK, supports BYOK model providers, and respects repository-level custom instructions files. This extends Copilot's footprint into the local Git client layer, which matters for Veeam's understanding of where AI-processed repo content flows outside the cloud platform perimeter.

GitHub Copilot CLI v1.0.67 shipped on June 30, 2026, adding Claude Sonnet 5 as a supported model, enforcing a minimum session limit of 30 AI credits, fixing MCP OAuth re-authentication failures against Microsoft Entra tenant vanity domains, and ensuring subagent sessions inherit parent tool restrictions. The addition of session credit floors and tighter subagent tool scoping are directly relevant to governing agentic workflows that touch repository data in CI/CD contexts.

As of June 1, 2026, GitHub Copilot completed its transition to usage-based billing, where every code completion, chat interaction, and code review consumes AI Credits against a monthly budget. Individual plan sign-ups were also paused in May 2026. This pricing restructuring changes how enterprises forecast AI tooling costs and may affect Veeam's own developer platform spend and license compliance posture across GitHub-hosted teams.

The GitHub Copilot SDK reached GA on June 2, 2026, enabling any application to embed Copilot's agentic engine — planning, tool invocation, file edits, streaming, and multi-turn sessions — via a stable API. It supports BYOK for OpenAI, Microsoft Foundry, and Anthropic, plus MCP server integration and an OpenTelemetry hook system. This is a significant new API surface: third-party backup and DevSecOps tools (including potential Veeam integrations) can now programmatically invoke Copilot agents against repository content.

GitLab 19.0 (released May 21, 2026) introduced a public beta Secrets Manager for Premium/Ultimate users that stores credentials within the same platform running code and pipelines, and restricts each secret to only authorized jobs. It also made SBOM dependency scanning generally available and extended the Duo Agent Platform across the full merge request lifecycle. The Secrets Manager represents a new internal credential store that Veeam must account for in backup scope: vault data co-located with pipeline config is a new recovery target category.

Atlassian announced that starting December 1, 2026, XML Site Export and XML Space Export in Confluence Cloud will no longer be officially supported and users proceed at their own risk. This directly impacts teams using XML export as an ad-hoc backup or migration mechanism for Confluence content. Veeam's Data Command Center messaging should call out that platform-native export tools are being sunset, reinforcing the need for a dedicated backup solution before the EOL date.