DevOps Platform Updates
scanned 113d ago8Latest announcements and changes from GitHub, GitLab, Azure DevOps, Bitbucket, and Atlassian.
Atlassian Enforces Points-Based Rate Limits on Jira and Confluence APIs
Effective March 2, 2026, Atlassian began phased enforcement of points-based quota rate limits for Jira and Confluence Cloud REST APIs. The rollout starts with a small percentage of apps and gradually expands over several weeks. Backup and data-protection integrations making high-volume API calls must implement rate-limit handling using the new unified structured headers (RateLimit, RateLimit-Policy).
Bitbucket OAuth 1.0 and Implicit Grant Removal Enforcement Underway
Bitbucket Cloud is actively running brownouts removing OAuth 1.0 and implicit grant flow support, with full removal on March 14, 2026. After that date, all OAuth 1.0 access tokens will permanently fail with HTTP 401. Any integrations authenticating to Bitbucket via legacy flows must migrate to OAuth 2.0 immediately.
GitHub Actions Self-Hosted Runner Pricing Now in Effect
As of March 1, 2026, GitHub charges $0.002 per minute for self-hosted runner usage in private repositories. This new cloud platform charge applies to all GitHub.com plans; Enterprise Server customers and public repos are exempt. GitHub estimates 96% of customers see no change, but teams with heavy self-hosted CI/CD workloads should review cost impact.
GitHub Actions Runner v2.329.0 Enforcement Brownout Active
GitHub is running brownout periods through March 16 that temporarily block registration of self-hosted runners older than v2.329.0. After March 16, runners below this version will be permanently blocked from connecting to GitHub Actions. Teams using Actions Runner Controller (ARC) must also verify runner container images meet the minimum version.
Bitbucket Cloud Service Disruption on March 6
Bitbucket Cloud was unavailable for affected users on March 6, 2026 due to a service disruption. The cause was identified and the incident was resolved the same day. Teams relying on Bitbucket for CI/CD triggers or repository-based backup operations should verify their resilience posture against platform outages.
GitHub Copilot Memory Enabled by Default for Pro Users
Copilot Memory is now enabled by default for all Copilot Pro and Pro+ users, building persistent repository-level understanding of codebases. Memories are scoped to individual repositories, validated against current code, and auto-expire after 28 days. This signals GitHub's push toward context-aware AI agents in code review and PR generation.
GitHub Now Sends Email Alerts for Usage Threshold Limits
GitHub introduced email notifications when included usage approaches monthly thresholds for Actions, Packages, Git LFS, and Codespaces. This helps organizations proactively manage consumption before hitting overage charges. Relevant for teams managing GitHub-hosted CI/CD pipelines or large artifact storage.
GitHub Copilot Metrics API Now Reports Plan Mode Telemetry
Copilot usage metrics now include plan mode telemetry under the chat_panel_plan_mode API key, enabling enterprises to track adoption and engagement. Supported in JetBrains, Eclipse, Xcode, and VS Code Insiders. This reclassification may cause an apparent dip in 'Custom' usage on dashboard charts.