GitLab.com is moving to 15.0 with a few breaking changes

GitLab 15.0 introduces significant updates, including new features and the removal of previously deprecated ones, reflecting its ongoing commitment to improving performance, scalability, and user experience. This major release includes breaking changes, such as the removal of audit events for repository push events, which were disabled by default due to performance concerns, and adjustments to the external status check API that now requires specific status fields. OAuth implicit grant authorization is no longer supported, and OAuth tokens must have an expiration. GitLab has enforced expiration on SSH keys and personal access tokens for enhanced security. Certain features, like required pipeline configurations, are now exclusive to the Ultimate tier, aligning with GitLab's tiering strategy. The release also discontinues support for the omniauth-kerberos gem, pushes rules to supersede CODEOWNERS, and introduces changes to the Runner API endpoints. The update affects various API fields and configuration settings, emphasizing a move towards more robust, secure integrations and modernized dependency management. The release also marks the end of support for certain languages and tools in Dependency Scanning, such as Python 3.6 and retire.js, and the deprecation of legacy infrastructure and features related to logging, tracing, and security protocols. Users are encouraged to transition to alternative solutions and updated configurations to ensure compatibility and leverage the latest GitLab capabilities.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.