# GitHub Issues Published articles for GitHub Issues. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Marketing ops as code: Automating events from planning to follow-up on GitHub DevFeed: [Marketing ops as code: Automating events from planning to follow-up on GitHub]() Original publisher: [Read original article]() Author: Tomoko Tanaka Published: 2026-09-11T18:26:10Z Content type: tutorial Language: en Sources: [GitHub Engineering]() Topics: [AI-assisted coding]() Tags: [ai-ml](), [api](), [automation](), [cli](), [events](), [github](), [github-actions](), [github-copilot](), [github-issues]() ### AI overview A GitHub marketing lead describes using GitHub Copilot and GitHub Actions to automate event operations from a GitHub Issue, including setup, daily registrant processing, and post-event cleanup. ### Source excerpt If you can write down how you do your work, you can automate it. Here's what I did to support GitHub's APAC marketing team. The post Marketing ops as code: Automating events from planning to follow-up on GitHub appeared first on The GitHub Blog. ## Visual Studio Code 1.137 DevFeed: [Visual Studio Code 1.137]() Original publisher: [Read original article]() Author: Visual Studio Code Team Published: 2026-09-09T17:00:00Z Content type: release Language: en Sources: [Visual Studio Code - Code Editing. Redefined.]() Topics: [vs-code](), [Automation](), [GitHub](), [GitHub Issues](), [Pull Request](), [GitHub Copilot]() Tags: [2026](), [article](), [automation](), [experimental](), [github](), [github-issues](), [pull-request](), [release](), [updates](), [visual-studio](), [voice](), [vs-code]() ### AI overview Visual Studio Code 1.137 introduces scheduled automations, experimental voice interaction with agents, workspace-attached quick chats, and GitHub issues and pull request details in the Agents window. ### Source excerpt Learn what's new in Visual Studio Code 1.137 Read the full article ## How we closed 1,500 GitHub issues in one month DevFeed: [How we closed 1,500 GitHub issues in one month]() Original publisher: [Read original article]() Author: Marcos Hernanz Published: 2026-09-04T04:00:00Z Content type: article Language: en Sources: [Next.js Blog]() Topics: [GitHub Issues](), [Next.js](), [AI-assisted coding](), [issue tracker](), [Maintainers](), [bug]() Tags: [agent](), [ai](), [bug](), [github-issues](), [issue-tracker](), [maintainers](), [next-js](), [sandbox](), [vercel]() ### AI overview The Next.js team describes using an AI research agent to help maintainers review an issue backlog, close outdated reports, and retain issues that still matter. ### Source excerpt How the Next.js team used an agent to research old reports and work through the issue backlog. ## Automating quality support at scale: AI and human in the loop DevFeed: [Automating quality support at scale: AI and human in the loop]() Original publisher: [Read original article]() Author: Hugo Casademont Published: 2026-08-18T00:00:00Z Content type: article Language: en Sources: [Windmill Blog]() Topics: [Artificial Intelligence](), [Claude](), [Discord](), [Slack](), [GitHub Issues](), [email](), [Linear](), [telemetry](), [WebSocket]() Tags: [ai](), [ai-windmill-support-claude](), [automated](), [claude](), [discord](), [email](), [github-issues](), [linear](), [slack](), [support](), [telemetry](), [windmill]() ### AI overview Windmill describes an internal support-automation pipeline that consolidates Discord, Slack, email, and GitHub issues into a Discord queue. It uses Claude and customer context to triage requests, draft replies and fixes, while requiring human approval before responses are sent. ### Source excerpt How does Windmill automate its own support? A Windmill pipeline funnels Discord, Slack and email tickets into one Discord queue, triages them with Claude, drafts replies, and dispatches fixes. ## Bugs, feature requests, career stories, and weekly readings 💡 DevFeed: [Bugs, feature requests, career stories, and weekly readings 💡]() Original publisher: [Read original article]() Author: Luca Rossi Published: 2026-08-03T07:01:44Z Content type: article Language: en Sources: [Refactoring]() Topics: [GitHub Issues](), [GitHub](), [Open Source](), [Artificial Intelligence]() Tags: [ai](), [bugs](), [career-stories](), [feature](), [github](), [github-issues](), [open-source](), [weekly]() ### AI overview This Monday Ideas newsletter discusses separating bugs from feature requests in product feedback workflows. It recommends routing submissions to the appropriate channels, deduplicating entries, and using intake workflows to turn valid work into tasks. It also includes career interview advice and a sponsored section about AI productivity and context. ### Source excerpt Monday Ideas -- Edition #219 ## Introducing Supabase Evals DevFeed: [Introducing Supabase Evals]() Original publisher: [Read original article]() Author: Matt Rossman Published: 2026-07-31T07:00:00Z Content type: article Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [AI-assisted coding](), [Benchmark](), [Open Source](), [coding](), [Command-line interface](), [MCP Server](), [Agent Skills](), [Database](), [debugging](), [observability](), [GitHub Issues]() Tags: [agent-skills](), [ai](), [ai-coding](), [benchmark](), [cli](), [coding](), [github-issues](), [mcp](), [mcp-server](), [open-source](), [testing]() ### AI overview Supabase introduces an open-source benchmark and framework for evaluating how well AI coding agents build with Supabase. It runs agents such as Claude Code, Codex, and OpenCode through realistic tasks, including schema construction, Edge Function debugging, and RLS policy fixes, then measures their performance in benchmark and regression suites. ### Source excerpt Our open-source benchmark for how well AI coding agents build with Supabase. ## Examples of Agent Goals, Loops, and Scheduled Workflows in Codex and Claude Code DevFeed: [Examples of Agent Goals, Loops, and Scheduled Workflows in Codex and Claude Code]() Original publisher: [Read original article]() Author: Owain Lewis Published: 2026-07-02T07:01:00Z Content type: article Language: en Sources: [The AI Engineer]() Topics: [codex](), [Loop Engineering](), [Automation](), [Claude Code](), [Pull Request](), [GitHub Issues](), [ci]() Tags: [agent](), [ai-agents](), [automation](), [ci](), [claude-code](), [codex](), [github-issues](), [logs](), [review](), [scheduled](), [tests](), [workflow]() ### AI overview The article explains how prompts, goals, recurring runs, and workflows differ, then presents examples of using agents for recurring engineering tasks. It emphasizes evidence, stop rules, tests, CI, logs, issues, pull requests, and human review as safeguards because agents can misunderstand context or make mistakes. ### Source excerpt Practical ways to combine prompts, goals, and scheduled runs in Codex and Claude Code. ## Seamless Crash Protection That Symbolicates Native Crashes DevFeed: [Seamless Crash Protection That Symbolicates Native Crashes]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-06-22T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [App](), [GitHub Issues](), [Cloud](), [Disk image](), [Android](), [iOS](), [Linux](), [macOS](), [Windows](), [tvOS](), [watchOS]() Tags: [android](), [cloud](), [crash](), [data](), [github-issues](), [ios](), [linux](), [macos](), [native](), [protection](), [retry](), [storage](), [watchos](), [win32](), [windows]() ### AI overview The article describes the new com.codename1.crash client, which captures crashes on devices, removes personal data before transmission, stores reports until upload succeeds, retries failed uploads, and uses cloud-side symbolication to file deduplicated reports as GitHub issues. It covers native crash support across multiple platforms and deobfuscation of Android exceptions. ### Source excerpt The new com.codename1.crash client captures crashes on device, scrubs personal data before anything is sent, retries reliably through a storage-first queue, and lets the build cloud symbolicate native crashes and file them as GitHub issues instead of emails. ## Native Linux, Apple Watch, A Game Builder And Crash Protection DevFeed: [Native Linux, Apple Watch, A Game Builder And Crash Protection]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-06-19T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [Linux](), [watchOS](), [GitHub Issues](), [Java](), [Kotlin](), [Programming]() Tags: [api](), [apple](), [apple-watch](), [crash](), [desktop](), [gaming](), [github-issues](), [java](), [kotlin](), [linux](), [native](), [watchos]() ### AI overview This weekly Codename One update describes a native Linux desktop port, Apple Watch and Wear OS support, a visual Game Builder with a high-level gaming API, and crash protection that symbolicates native crashes and files them as GitHub issues. It also notes a rebuild of the build cloud and related failed builds. ### Source excerpt This week adds a native Linux desktop port, an Apple Watch and Wear OS port, a visual Game Builder with a high-level gaming API, and seamless crash protection that symbolicates native crashes and files them as GitHub issues. ## How I'm building autonomous agent loops DevFeed: [How I'm building autonomous agent loops]() Original publisher: [Read original article]() Author: Owain Lewis Published: 2026-06-13T14:02:17Z Content type: tutorial Language: en Sources: [The AI Engineer]() Topics: [Loop Engineering](), [Artificial Intelligence](), [GitHub Issues](), [Claude Code](), [codex](), [GitHub]() Tags: [agent](), [ai](), [autonomous](), [claude-code](), [codex](), [github-issues](), [loops](), [workflow]() ### AI overview This guide explains how to build autonomous agent loops in which agents read project state, perform work, update that state, and repeat on a schedule or in response to events. It presents GitHub Issues as a control plane and describes manager and worker loops built with Claude Code and Codex, including risk classification, ticket management, and safeguards against destructive actions. ### Source excerpt A guide on loop engineering and autonomous AI loops ## PowerShell is now notarized and hardened for macOS DevFeed: [PowerShell is now notarized and hardened for macOS]() Original publisher: [Read original article]() Author: Jason Helmick Published: 2026-05-21T14:40:15Z Content type: release Language: en Sources: [PowerShell Team]() Topics: [PowerShell](), [macOS](), [Security](), [PowerShell Release](), [GitHub Issues]() Tags: [apple](), [developer](), [documentation](), [github-issues](), [macos](), [microsoft](), [powershell](), [powershell-macos](), [product](), [release](), [releases](), [security](), [software](), [update]() ### AI overview PowerShell packages for macOS are now notarized and hardened to meet Apple security requirements and Microsoft compliance standards. The update also fixes tarball file permissions and is included in PowerShell 7.4 and later maintenance releases. ### Source excerpt PowerShell for macOS is now properly notarized and hardened, meeting both Apple and Microsoft security requirements. The post PowerShell is now notarized and hardened for macOS appeared first on PowerShell Team. ## From latency to instant: Modernizing GitHub Issues navigation performance DevFeed: [From latency to instant: Modernizing GitHub Issues navigation performance]() Original publisher: [Read original article]() Author: Natalie Guevara Published: 2026-05-14T16:00:00Z Content type: article Language: en Sources: [GitHub]() Topics: [GitHub Issues](), [Latency](), [Caching](), [client](), [Web]() Tags: [architecture](), [architecture-optimization](), [caching](), [engineering](), [github](), [github-issues](), [latency](), [local](), [performance](), [web-performance]() ### AI overview The GitHub Issues team describes how it improved navigation performance by moving work to the client, rendering from locally cached data, and revalidating in the background. The approach uses IndexedDB, preheating, and a service worker to reduce perceived latency, while acknowledging implementation tradeoffs. ### Source excerpt How the GitHub Issues team used client-side caching, smart prefetching, and service workers to make navigation feel instant. The post From latency to instant: Modernizing GitHub Issues navigation performance appeared first on The GitHub Blog. ## Podman Standups! DevFeed: [Podman Standups!]() Original publisher: [Read original article]() Author: tsweeney Published: 2026-05-01T17:21:55Z Content type: article Language: en Sources: [blog.podman.io]() Topics: [podman](), [GitHub Issues]() Tags: [2026](), [cncf](), [community](), [events](), [github-issues](), [podman](), [red-hat](), [team](), [uncategorized](), [video]() ### AI overview The Podman project is moving its recurring standup meetings to the CNCF calendar so the wider community can join. Meetings will occur on Mondays and Thursdays, beginning May 4, 2026, with status roundtables followed by optional discussion topics. The existing Podman Community Cabal meeting will end after May 5, 2026. ### Source excerpt The standups are coming, the standups are coming! Come one, come all to the Podman Standup Meetings! For the past many years, the Podman team at Red Hat has held standup meetings on Mondays at 10:00 a.m. Eastern, and also on Thursdays at 11:00 a.m. Eastern. (Currently UTC-4, then UTC-5 once the USA goes to [...] ## Qinglong task scheduler RCE vulnerabilities exploited in the wild for cryptomining DevFeed: [Qinglong task scheduler RCE vulnerabilities exploited in the wild for cryptomining]() Original publisher: [Read original article]() Author: Julia Kinday Published: 2026-04-27T00:00:00Z Content type: news Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Vulnerabilities](), [incident](), [Security](), [Express](), [GitHub Issues](), [Docker](), [GitHub](), [Open Source](), [Server](), [Shell](), [JavaScript](), [npm]() Tags: [application-security](), [attacks](), [auth](), [authentication](), [awareness](), [blog](), [ci-cd](), [cloud](), [cloud-security](), [code](), [developer](), [devops](), [docker](), [enablement](), [github](), [github-issues](), [incident](), [javascript](), [malware](), [node-js](), [open-source](), [open-source-security](), [routing](), [security](), [security-labs](), [self-hosted](), [servers](), [snyk-code](), [snyk-container](), [snyk-learn](), [snyk-open-source](), [snyk-security-intel](), [tech](), [typescript](), [vulnerabilities](), [vulnerability]() ### AI overview Qinglong, an open-source self-hosted task scheduling panel, was exploited through two authentication bypass vulnerabilities affecting versions 2.20.1 and earlier. Attackers used unauthenticated remote code execution to deploy cryptocurrency miners on publicly accessible installations. The article describes the vulnerabilities, their Express.js routing and middleware flaws, and the impact on operators using cloud VPS instances and home servers. ### Source excerpt Two authentication bypass vulnerabilities (CVE-2026-3965, CVE-2026-4047) in the Qinglong task scheduling panel were exploited in the wild to deploy cryptomining malware. Here's what happened, how the attacks worked, and what self-hosted application operators should learn from this incident. ## Behind the Scenes: How Maintaining Cloud Native Buildpacks Powers Platforms Like Heroku DevFeed: [Behind the Scenes: How Maintaining Cloud Native Buildpacks Powers Platforms Like Heroku]() Original publisher: [Read original article]() Author: Juan Bustamante Published: 2026-03-17T15:00:03Z Content type: opinion Language: en Sources: [Heroku]() Topics: [Heroku](), [Maintainers](), [Cloud Native Ecosystem](), [Command-line interface](), [releases](), [Security](), [vulnerability](), [GitHub Actions](), [GitHub](), [GitHub Issues](), [Google Cloud Platform (GCP)](), [Docker]() Tags: [buildpacks](), [cli](), [cloud](), [cloud-infrastructure](), [cloud-native](), [cloud-native-ecosystem](), [docker](), [ecosystem](), [engineering](), [github](), [github-actions](), [github-issues](), [google-cloud](), [google-cloud-run](), [heroku](), [maintainers](), [maintenance](), [open-source](), [patches](), [platform](), [releases](), [security](), [vulnerability]() ### AI overview This article describes how pack CLI maintainers support Cloud Native Buildpacks through releases, security patches, issue triage, pull request reviews, CI changes, and feature development. It explains how Heroku-funded maintenance benefits Heroku, Google Cloud Run, and internal platform teams. ### Source excerpt Most developers never see the 11 pack releases we shipped in the last 14 months as pack CLI maintainers. That's actually a good sign--it means the infrastructure just works. When a critical vulnerability emerges requiring an immediate upgrade, the fix is shipped within days. Here's what most developers don't see: that same security patch now [...] The post Behind the Scenes: How Maintaining Cloud Native Buildpacks Powers Platforms Like Heroku appeared first on Heroku. ## Knowledge management systems for technical teams DevFeed: [Knowledge management systems for technical teams]() Original publisher: [Read original article]() Author: Peri Langlois Published: 2026-03-06T00:00:00Z Content type: tutorial Language: en Sources: [Mintlify Blog]() Topics: [knowledge-management](), [systems](), [Documentation](), [Code](), [Git](), [GitHub](), [GitHub Issues](), [Wiki](), [Google]() Tags: [best-practices](), [code](), [developer](), [documentation](), [engineering](), [git](), [github](), [github-issues](), [google](), [how-to](), [knowledge-management](), [slack](), [technical](), [wikis]() ### AI overview This guide explains developer knowledge management systems as connected ecosystems of code, documentation, architecture records, tests, and operational guides. It describes how these systems help engineers find accurate information and remain productive, and why they must evolve alongside code rather than rely only on static documents. ### Source excerpt Learn what makes developer knowledge management systems successful, and how to build systems that engineering teams will actually use and get value from. ## How I Built an Autonomous Development System with AI Agents DevFeed: [How I Built an Autonomous Development System with AI Agents]() Original publisher: [Read original article]() Published: 2026-02-16T14:00:00Z Content type: tutorial Language: en Sources: [Antonio Leiva]() Topics: [Android](), [Loop Engineering](), [Development](), [GitHub Issues](), [codex](), [Next.js](), [PostgreSQL](), [Prisma](), [Redis]() Tags: [agents](), [ai](), [automation](), [codex](), [development](), [github-issues](), [next-js](), [postgresql](), [prisma](), [redis](), [security]() ### AI overview The author describes an autonomous development system for the Learnfolx training platform. Specialized scanners identify problems and create GitHub issues, a triage process prioritizes them, and an executor implements fixes and closes issues. Smoke tests provide periodic verification. The system uses Codex App automations and an external cron, with reported results including 80 issues created and about 50 closed in three days. ### Source excerpt Everything Android, Kotlin and other random topics ## I've created a website to track the team's activity DevFeed: [I've created a website to track the team's activity]() Original publisher: [Read original article]() Author: Alexey Milovidov Published: 2025-11-10T00:00:00Z Content type: article Language: en Sources: [ClickHouse Blog]() Topics: [GitHub Issues](), [Database](), [Bun](), [elasticsearch](), [PyTorch](), [Chromium]() Tags: [clickhouse](), [database](), [developer-productivity](), [github](), [github-issues](), [metrics](), [pull-requests](), [sql]() ### AI overview The article introduces a website for comparing GitHub repository activity metrics and argues that commits, pull requests, and issue counts should be interpreted as secondary signals rather than productivity targets. ### Source excerpt Initially, I wanted to make a single report to incentivise for looking at and resolving GitHub issues. But I'm greedy, so in the end it appeared to be a website where you can compare various metrics on team activities across GitHub repositories. ## AI Workflows for Docs: Putting Devin to Work DevFeed: [AI Workflows for Docs: Putting Devin to Work]() Original publisher: [Read original article]() Author: Daniel Price Published: 2025-06-23T17:10:34Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [AI Bots]() Tags: [agent](), [agents](), [ai](), [changelog](), [docs](), [github](), [github-issues](), [ocr](), [product](), [pull-request](), [workflows]() ### AI overview Neon's documentation team describes using Devin, an AI agent that opens pull requests, to automate repetitive documentation workflows. Examples include setting up changelogs, addressing GitHub issues and PRs, and adding a relevant repository image while documenting a feature. ### Source excerpt At Neon, our docs team does a little bit of everything. We work on technical documentation, sometimes UI copy, changelogs, reviews, and the occasional regex-heavy cleanup across hundreds of pages. It's a lot of small, steady work - often, exactly the kind of work you wish an AI a... ## Building a Privacy-First Feedback Widget DevFeed: [Building a Privacy-First Feedback Widget]() Original publisher: [Read original article]() Published: 2025-06-13T00:00:00Z Content type: article Language: en Sources: [The Nuxt Blog]() Topics: [Nuxt.js](), [Documentation](), [Vue.js](), [Drizzle](), [Developer experience](), [User Experience](), [API](), [data](), [GitHub Issues]() Tags: [api](), [article](), [data](), [database](), [documentation](), [drizzle](), [frontend](), [gdpr](), [github-issues](), [nuxt](), [privacy](), [source](), [user-experience](), [validation](), [vue]() ### AI overview Nuxt describes the design and implementation of a privacy-first feedback widget for its documentation. The widget uses Vue 3, Motion for Vue, Drizzle, and a database-backed server workflow to collect feedback with minimal interaction, daily deduplication, and no persistent personal tracking. ### Source excerpt A lightweight, privacy-focused widget to gather your feedback on Nuxt documentation, built with Drizzle, NuxtHub database and Motion Vue. ## Devstral DevFeed: [Devstral]() Original publisher: [Read original article]() Published: 2025-05-21T12:00:00Z Content type: release Language: en Sources: [Mistral AI Blog]() Topics: [AI-assisted coding](), [Large Language Model](), [Benchmark](), [Open Source](), [GitHub Issues](), [Deployment](), [Security](), [Software Engineering]() Tags: [agentic-coding](), [ai](), [benchmark](), [github-issues](), [llm](), [local](), [models](), [open](), [open-source](), [security]() ### AI overview Mistral AI and All Hands AI introduce Devstral, an Apache 2.0-licensed agentic LLM for software engineering. The article reports a 46.8% score on SWE-Bench Verified, says Devstral outperforms prior open-source models and several larger or closed models, and describes local, on-device, enterprise, and agentic coding use cases. ### Source excerpt The most powerful AI platform for enterprises. Customize, fine-tune, and deploy AI assistants, autonomous agents, and multimodal AI with open models. ## Changing comments provider for my blog DevFeed: [Changing comments provider for my blog]() Original publisher: [Read original article]() Author: Tom Published: 2023-12-26T00:00:00Z Content type: article Language: en Sources: [Tomasz Gągor]() Topics: [Hugo](), [Giscus](), [GitHub](), [GitHub Issues]() Tags: [ad-free-comments](), [blog](), [blog-comments-system](), [experience](), [giscus-comments](), [github](), [github-issues](), [hugo](), [hugo-comments-provider](), [switching](), [switching-from-disqus](), [utterances-comments]() ### AI overview The author describes switching a Hugo blog away from Disqus after it began showing ads. They compare Utterances, which stores comments in GitHub Issues, with Giscus, which uses GitHub Discussions, and initially configure Utterances. ### Source excerpt Explore the process of switching comments provider for a Hugo blog, comparing Disqus, Utterances, and Giscus for better user engagement and ad-free experience. ## Mintlify Launch Week Recap: CLI, Docs Feedback, Global CSS, API Playground, and Web Editor DevFeed: [Mintlify Launch Week Recap: CLI, Docs Feedback, Global CSS, API Playground, and Web Editor]() Original publisher: [Read original article]() Author: Han Wang Published: 2023-10-02T00:00:00Z Content type: article Language: en Sources: [Mintlify Blog]() Topics: [Command-line interface](), [Documentation](), [Web Development](), [CSS](), [GitHub](), [GitHub Issues]() Tags: [announcements](), [cli](), [css](), [documentation](), [github](), [github-issues](), [hot-reloading]() ### AI overview The article recaps five Mintlify features released during Launch Week: CLI enhancements, Docs Feedback, Global CSS, a redesigned API Playground, and a Web Editor. It highlights CLI size and installation-time reductions, feedback and analytics capabilities, design customization, and browser-based editing with live preview. ### Source excerpt Last week, we launched a feature a day, from CLI enhancements to Global CSS to the Web Editor. ## New Keycloak maintainer: Alexander Schwartz DevFeed: [New Keycloak maintainer: Alexander Schwartz]() Original publisher: [Read original article]() Author: Bruno Oliveira Published: 2023-06-27T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [Benchmark](), [Documentation](), [GitHub](), [GitHub Issues](), [pull-requests]() Tags: [benchmark](), [bug-fixes](), [documentation](), [github](), [github-issues](), [idm](), [kerberos](), [keycloak](), [ldap](), [new-features](), [openid-connect](), [pull-requests](), [saml](), [sso]() ### AI overview Keycloak announces Alexander Schwartz as an official maintainer, highlighting his contributions to the project, including work on its store, documentation, benchmark project, community discussions, pull requests, features, bug fixes, and issue triage. ### Source excerpt We're delighted to announce Alexander Schwartz as an official maintainer of Keycloak. Alexander started contributing to Keycloak in 2015. He applied it in several customer installations and is maintaining the Dropwizard module for Keycloak. In January 2022, he joined Red Hat. Since then, he has contributed to Keycloak's store and documentation and is the key contributor to the Keycloak benchmark project. He helped with Keycloak's submission to CNCF, and represented Keycloak at KubeCon Amsterdam in April 2023. He has shown his commitment to the Keycloak community by collaborating on design discussions, participating in GitHub discussions, reviewing pull-requests, answering questions on the Keycloak mailing lists, contributing to new features, bug fixes and triaging GitHub issues. The Keycloak team is very excited to welcome Alexander as our new maintainer and long-time contributor. [Next page]()