<?xml version='1.0' encoding='UTF-8'?>
<feed xmlns:webfeeds="http://webfeeds.org/rss/1.0" xmlns:media="http://search.yahoo.com/mrss/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://about.gitlab.com/</id>
  <title>GitLab</title>
  <updated>2026-11-12T00:59:01.304923+00:00</updated>
  <author>
    <name>Various</name>
  </author>
  <link href="https://trvny.github.io/feedseek/gitlab.xml" rel="self"/>
  <link href="https://about.gitlab.com/" rel="alternate"/>
  <generator uri="https://github.com/trvny/feedseek">Feedseek</generator>
  <icon>https://feeds-proxy.travny.workers.dev/favicon?domain=about.gitlab.com&amp;sz=64</icon>
  <logo>https://feeds-proxy.travny.workers.dev/favicon?domain=about.gitlab.com&amp;sz=256</logo>
  <webfeeds:logo>https://feeds-proxy.travny.workers.dev/favicon?domain=about.gitlab.com&amp;sz=256</webfeeds:logo>
  <webfeeds:icon>https://feeds-proxy.travny.workers.dev/favicon?domain=about.gitlab.com&amp;sz=64</webfeeds:icon>
  <subtitle>Combined GitLab and federated forge feed: GitLab blog, release notes, patch releases, press releases and what's new, plus Codeberg and Forgejo.</subtitle>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/4401a76717dfbb1d</id>
    <title>How to prevent leaks from Claude Code's 'Don't ask again' file</title>
    <updated>2026-11-11T00:00:00+00:00</updated>
    <content>This guide details how to find and remove secrets that were inadvertently committed to projects and repositories hosted on GitLab. We’ve confirmed that GitLab’s own infrastructure secrets are protected. In Claude Code, Anthropic’s coding agent, a developer can approve a shell command by selecting “Yes, and don’t ask again.” Claude then saves that exact command to .claude/settings.local.json in the project folder and runs it without asking in the future. If the command contained a password or a t</content>
    <link href="https://about.gitlab.com/blog/prevent-leaks-from-claude-code-dont-ask-again-file/" rel="alternate"/>
    <category term="GitLab Blog" label="GitLab Blog"/>
    <published>2026-11-11T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1782237704/cj50chkvprjthczevmog.png" type="image/png" medium="image"/>
      <media:thumbnail url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1782237704/cj50chkvprjthczevmog.png"/>
    </media:group>
    <dc:creator>GitLab Blog</dc:creator>
    <link rel="enclosure" href="https://res.cloudinary.com/about-gitlab-com/image/upload/v1782237704/cj50chkvprjthczevmog.png" type="image/png" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/56abcd5235c93954</id>
    <title>GitLab Critical Patch Release: 19.5.4, 19.4.6, 19.3.8</title>
    <updated>2026-11-10T00:00:00+00:00</updated>
    <content>On November 10, 2026, we released versions 19.5.4, 19.4.6, 19.3.8 for GitLab Community Edition and Enterprise Edition. These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to
one of these versions immediately.
GitLab.com and GitLab Dedicated are already running a patched version. GitLab.com and GitLab Dedicated customers do not need to take action. GitLab releases fixes for vulnerabilities in patch releases. The</content>
    <link href="https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-4-released/" rel="alternate"/>
    <category term="GitLab Patch Releases" label="GitLab Patch Releases"/>
    <published>2026-11-10T00:00:00+00:00</published>
    <dc:creator>GitLab Patch Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/fa372ae0dfc5072f</id>
    <title>How to design a decision-grade pilot for agentic AI</title>
    <updated>2026-11-09T00:00:00+00:00</updated>
    <content>Agentic AI changes the nature of a technology evaluation. When an AI system only generates an answer, a person reviews the output and decides whether to use it. An agent goes further: It gathers context, selects tools, makes decisions, and executes a sequence of actions across the software development lifecycle. The central question for a pilot is therefore not whether the agent can produce an impressive result. It is: What evidence would be sufficient to authorize this agent to perform this wor</content>
    <link href="https://about.gitlab.com/blog/how-to-develop-a-decision-grade-ai-pilot/" rel="alternate"/>
    <category term="GitLab Blog" label="GitLab Blog"/>
    <published>2026-11-09T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1774957323/xfnzvlwc4c2vhal3v3jv.png" type="image/png" medium="image"/>
      <media:thumbnail url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1774957323/xfnzvlwc4c2vhal3v3jv.png"/>
    </media:group>
    <dc:creator>GitLab Blog</dc:creator>
    <link rel="enclosure" href="https://res.cloudinary.com/about-gitlab-com/image/upload/v1774957323/xfnzvlwc4c2vhal3v3jv.png" type="image/png" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/c0584ddacd353de1</id>
    <title>The Pentagon wants to know who checks code when AI writes it</title>
    <updated>2026-11-06T00:00:00+00:00</updated>
    <content>The Department of War now treats AI-generated code as unverified until it’s proven otherwise. DoW Instruction 8430.01 , “Accelerated Mission Software,” took effect September 8, 2026, and is the department’s latest guidance on modernizing and managing software. If you build or buy software for the DoW, the instruction changes what’s required of you for every line AI writes. You have to review and test it to the same standard as human-written code, show where AI touched it, and keep it on systems </content>
    <link href="https://about.gitlab.com/blog/department-of-war-instruction-for-ai-generated-code/" rel="alternate"/>
    <category term="GitLab Blog" label="GitLab Blog"/>
    <published>2026-11-06T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1776347152/unw3mzatkd5xyfbzcnni.png" type="image/png" medium="image"/>
      <media:thumbnail url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1776347152/unw3mzatkd5xyfbzcnni.png"/>
    </media:group>
    <dc:creator>GitLab Blog</dc:creator>
    <link rel="enclosure" href="https://res.cloudinary.com/about-gitlab-com/image/upload/v1776347152/unw3mzatkd5xyfbzcnni.png" type="image/png" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/8ad33143ba46d118</id>
    <title>10 questions to ask any software vendor about sovereignty</title>
    <updated>2026-11-02T00:00:00+00:00</updated>
    <content>Sovereignty is moving from buzzword to buying criterion. The European Commission’s proposed Cloud and AI Development Act (CADA) would set assurance levels for the cloud and AI services public authorities buy, defining where data should live and who can access it. Parts of it could reach private entities too. GitLab submitted its own comment on CADA because we share the goal of strengthening Europe’s digital sovereignty and security. We believe this important work should prioritize customer contr</content>
    <link href="https://about.gitlab.com/blog/10-questions-to-ask-any-software-vendor-about-sovereignty/" rel="alternate"/>
    <category term="GitLab Blog" label="GitLab Blog"/>
    <published>2026-11-02T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1785336708/ww4mlighwlvvzgnmbe6w.png" type="image/png" medium="image"/>
      <media:thumbnail url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1785336708/ww4mlighwlvvzgnmbe6w.png"/>
    </media:group>
    <dc:creator>GitLab Blog</dc:creator>
    <link rel="enclosure" href="https://res.cloudinary.com/about-gitlab-com/image/upload/v1785336708/ww4mlighwlvvzgnmbe6w.png" type="image/png" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/2e163eafdcd97ad3</id>
    <title>Removing OpenID 2.0 Support</title>
    <updated>2026-11-02T00:00:00+00:00</updated>
    <content>Forgejo is removing OpenID Authentication 2.0 support in 2027.</content>
    <link href="https://forgejo.org/2026-11-removing-openid/" rel="alternate"/>
    <category term="Forgejo" label="Forgejo"/>
    <published>2026-11-02T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" medium="image"/>
      <media:thumbnail url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp"/>
    </media:group>
    <dc:creator>Forgejo</dc:creator>
    <link rel="enclosure" href="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/25a8884aa6560c90</id>
    <title>GitLab Orbit is GA: Higher agent accuracy, lower token cost</title>
    <updated>2026-10-29T00:00:00+00:00</updated>
    <content>An agent’s true cost isn’t only the tokens it burns. It’s the review that calls your code “safe to merge” after seeing the diff, but without any context on the pipeline. We call that artificial confidence, not artificial intelligence. Agents guess because code is all they can see; they can’t see the merge request that last changed it, the pipeline that ran it, the vulnerability it carries, or the people who wrote and reviewed it. Guessing is expensive. If you’ve tried running agents in a large m</content>
    <link href="https://about.gitlab.com/blog/gitlab-orbit-ga/" rel="alternate"/>
    <category term="GitLab Blog" label="GitLab Blog"/>
    <published>2026-10-29T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1793223579/kwn4st4vqqylpf3lhkic.png" type="image/png" medium="image"/>
      <media:thumbnail url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1793223579/kwn4st4vqqylpf3lhkic.png"/>
    </media:group>
    <dc:creator>GitLab Blog</dc:creator>
    <link rel="enclosure" href="https://res.cloudinary.com/about-gitlab-com/image/upload/v1793223579/kwn4st4vqqylpf3lhkic.png" type="image/png" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/0c85ec4e8428ce5b</id>
    <title>GitLab Orbit: Find vulnerability blast radius without the manual hunt</title>
    <updated>2026-10-29T00:00:00+00:00</updated>
    <content>A critical vulnerability needs a fix and a map. The fix is usually fast. Finding where the vulnerable component lives, who owns it, and whether it's exposed to the Internet is what costs you time. Most security teams piece that answer together from scanner reports, spreadsheets, and a Slack thread asking who owns a service nobody recognizes, and you stay exposed for every hour that takes. GitLab Orbit , now generally available , replaces this manual work with a single query. Orbit connects code,</content>
    <link href="https://about.gitlab.com/blog/find-vulnerability-blast-radius-with-gitlab-orbit/" rel="alternate"/>
    <category term="GitLab Blog" label="GitLab Blog"/>
    <published>2026-10-29T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1780996524/sd1vpl8empy26wizarqj.png" type="image/png" medium="image"/>
      <media:thumbnail url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1780996524/sd1vpl8empy26wizarqj.png"/>
    </media:group>
    <dc:creator>GitLab Blog</dc:creator>
    <link rel="enclosure" href="https://res.cloudinary.com/about-gitlab-com/image/upload/v1780996524/sd1vpl8empy26wizarqj.png" type="image/png" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/e30ab49652d6854c</id>
    <title>GitLab Patch Release and Security Update: 19.5.3, 19.4.5, 19.3.7, 19.2.10, 19.1.10, 19.0.11, 18.11.14</title>
    <updated>2026-10-29T00:00:00+00:00</updated>
    <content>On October 29, 2026, we released versions 19.5.3, 19.4.5, 19.3.7, 19.2.10, 19.1.10, 19.0.11, 18.11.14 for GitLab Community Edition (CE) and Enterprise Edition (EE). GitLab.com is already running the patched version. GitLab Dedicated tenants running 19.4.3-internal0 or later already include these fixes and do not need to take action. We also released version 19.5.1 for GitLab Runner and released versions 18.11.8, 19.0.13, 19.1.9, 19.2.5, 19.3.3, 19.4.3, 19.5.3 for GitLab AI Gateway. These version</content>
    <link href="https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-3-released/" rel="alternate"/>
    <category term="GitLab Patch Releases" label="GitLab Patch Releases"/>
    <published>2026-10-29T00:00:00+00:00</published>
    <dc:creator>GitLab Patch Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/84e1d648411349bc</id>
    <title>What happens when vulnerabilities are discovered faster than you can fix them?</title>
    <updated>2026-10-28T00:00:00+00:00</updated>
    <content>We're entering a new era of application security. Frontier AI models are uncovering complex flaws that traditional tools overlooked, and attackers are using the same models to exploit them faster. Remediation isn't keeping pace: Verizon's 2026 Data Breach Investigations Report (DBIR) measures the median time to fully remediate a known-exploited vulnerability at 43 days, up from 32 in 2025. Security teams are already stretched across growing application portfolios, third-party dependencies, and a</content>
    <link href="https://about.gitlab.com/blog/security-at-machine-speed/" rel="alternate"/>
    <category term="GitLab Blog" label="GitLab Blog"/>
    <published>2026-10-28T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1772195014/ooezwusxjl1f7ijfmbvj.png" type="image/png" medium="image"/>
      <media:thumbnail url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1772195014/ooezwusxjl1f7ijfmbvj.png"/>
    </media:group>
    <dc:creator>GitLab Blog</dc:creator>
    <link rel="enclosure" href="https://res.cloudinary.com/about-gitlab-com/image/upload/v1772195014/ooezwusxjl1f7ijfmbvj.png" type="image/png" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/f6d1ef252c6c7841</id>
    <title>Extend GitLab Duo Agent Platform into your business systems</title>
    <updated>2026-10-27T00:00:00+00:00</updated>
    <content>Developers mostly use GitLab Duo Agent Platform where they already work: the IDE, merge requests, and issues. But DevSecOps teams also support the business systems the rest of the company runs on, and those systems break too. In Salesforce, for example, when a validation fails, a callout times out, or a null slips through a trigger, the error gets logged, but the log doesn’t explain the cause. An engineer still has to read the stack trace, find the class in the repository, check what changed rec</content>
    <link href="https://about.gitlab.com/blog/extend-gitlab-duo-agent-platform-into-your-business-systems/" rel="alternate"/>
    <category term="GitLab Blog" label="GitLab Blog"/>
    <published>2026-10-27T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1793038948/do3owb7ivg2uqixoeiqo.jpg" type="image/jpeg" medium="image"/>
      <media:thumbnail url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1793038948/do3owb7ivg2uqixoeiqo.jpg"/>
    </media:group>
    <dc:creator>GitLab Blog</dc:creator>
    <link rel="enclosure" href="https://res.cloudinary.com/about-gitlab-com/image/upload/v1793038948/do3owb7ivg2uqixoeiqo.jpg" type="image/jpeg" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/66c2d9e3656310b2</id>
    <title>Pillow CVE-2026-112900: How to find and fix it with GitLab</title>
    <updated>2026-10-26T00:00:00+00:00</updated>
    <content>GitLab is not affected by CVE-2026-112900 or the other vulnerabilities fixed in Pillow 13.0.0. GitLab products do not include the Pillow library, and our Security team has found no evidence of impact to GitLab-managed infrastructure. GitLab.com, GitLab Self-Managed, and GitLab Dedicated are not impacted. Pillow is one of the most widely used image libraries in the Python ecosystem. It often sits several layers down in a dependency tree, pulled in by a web framework, a thumbnailing service or an </content>
    <link href="https://about.gitlab.com/blog/pillow-cve-find-and-fix-with-gitlab/" rel="alternate"/>
    <category term="GitLab Blog" label="GitLab Blog"/>
    <published>2026-10-26T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1793049447/qw4yuepojec1q89qkas4.png" type="image/png" medium="image"/>
      <media:thumbnail url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1793049447/qw4yuepojec1q89qkas4.png"/>
    </media:group>
    <dc:creator>GitLab Blog</dc:creator>
    <link rel="enclosure" href="https://res.cloudinary.com/about-gitlab-com/image/upload/v1793049447/qw4yuepojec1q89qkas4.png" type="image/png" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/6cdadcab7b70fcc3</id>
    <title>PHP2Shell: GitLab helps find and remediate critical PHP flaws</title>
    <updated>2026-10-22T00:00:00+00:00</updated>
    <content>GitLab is not affected by PHP2Shell (CVE-2026-109618 and CVE-2026-109619). The GitLab application is not written in PHP and does not run it to serve web requests, and our Security team has found no evidence of impact to GitLab-managed infrastructure. GitLab.com, GitLab Self-Managed, and GitLab Dedicated are not impacted. PHP is a widely used programming language that runs on web servers and powers popular platforms like WordPress, Drupal, and Magento, so a flaw in PHP itself can affect many webs</content>
    <link href="https://about.gitlab.com/blog/gitlab-helps-remediate-critical-php-flaws/" rel="alternate"/>
    <category term="GitLab Blog" label="GitLab Blog"/>
    <published>2026-10-22T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1792694702/ahsysxh1p9u2rymcxhco.png" type="image/png" medium="image"/>
      <media:thumbnail url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1792694702/ahsysxh1p9u2rymcxhco.png"/>
    </media:group>
    <dc:creator>GitLab Blog</dc:creator>
    <link rel="enclosure" href="https://res.cloudinary.com/about-gitlab-com/image/upload/v1792694702/ahsysxh1p9u2rymcxhco.png" type="image/png" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/9c3fe8f01f4a5c7a</id>
    <title>GitLab Critical Patch Release: 19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10, 18.11.13</title>
    <updated>2026-10-21T00:00:00+00:00</updated>
    <content>On October 21, 2026, we released versions 19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10, 18.11.13 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to
one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated tenants running 19.3.5-internal0 and 19.4.2-internal0 or later already include these fixes an</content>
    <link href="https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-1-released/" rel="alternate"/>
    <category term="GitLab Patch Releases" label="GitLab Patch Releases"/>
    <published>2026-10-21T00:00:00+00:00</published>
    <dc:creator>GitLab Patch Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/00d9b547b024d811</id>
    <title>Redesign how your team ships software with AI agents</title>
    <updated>2026-10-20T00:00:00+00:00</updated>
    <content>AI agents are sending more and more code into review queues built for human-paced work. A coding assistant can speed up code writing, but it can’t show you whether review, security checks, and release approvals can keep pace with all that extra code. AI-native engineering — the practice of intentionally designing the engineering process so people and agents each do what they are best suited to — starts with identifying delivery bottlenecks, then deciding how much autonomy agents should have and </content>
    <link href="https://about.gitlab.com/blog/redesign-how-your-team-ships-software-with-ai-agents/" rel="alternate"/>
    <category term="GitLab Blog" label="GitLab Blog"/>
    <published>2026-10-20T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1790265004/jadfgmjgjrdomp0liolj.png" type="image/png" medium="image"/>
      <media:thumbnail url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1790265004/jadfgmjgjrdomp0liolj.png"/>
    </media:group>
    <dc:creator>GitLab Blog</dc:creator>
    <link rel="enclosure" href="https://res.cloudinary.com/about-gitlab-com/image/upload/v1790265004/jadfgmjgjrdomp0liolj.png" type="image/png" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/f535ba213eb7b39f</id>
    <title>AI Governance: One view of agent activity</title>
    <updated>2026-10-20T00:00:00+00:00</updated>
    <content>AI coding agents are writing and changing code, from GitLab Duo Agent Platform agents to externally connected agents like Claude Code, Cursor, and Codex. You are accountable for what those agents do, yet most of their activity stays invisible: which agents ran, who used them, and what they touched. Teams often struggle with understanding whether a developer used a tool or model that is approved or not. The AI Governance Dashboard, now in beta, gives you one place to see agent activity across you</content>
    <link href="https://about.gitlab.com/blog/ai-governance-dashboard/" rel="alternate"/>
    <category term="GitLab Blog" label="GitLab Blog"/>
    <published>2026-10-20T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1792498520/if5duyy9qojp7qsizn0i.png" type="image/png" medium="image"/>
      <media:thumbnail url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1792498520/if5duyy9qojp7qsizn0i.png"/>
    </media:group>
    <dc:creator>GitLab Blog</dc:creator>
    <link rel="enclosure" href="https://res.cloudinary.com/about-gitlab-com/image/upload/v1792498520/if5duyy9qojp7qsizn0i.png" type="image/png" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/20e33ff4241b2256</id>
    <title>Uncover the business logic vulnerabilities SAST scanners miss</title>
    <updated>2026-10-20T00:00:00+00:00</updated>
    <content>Broken object-level authorization ranks first on the OWASP API Security Top 10 , and OWASP says that traditional static application security testing (SAST) tools struggle to find access control flaws. A missing authorization check is an absence of code, so a scanner that matches patterns has nothing to match. You can find the gap only if you already know what the endpoint is meant to enforce. We're building Business Logic Security Analyzer in GitLab Duo Agent Platform to catch business logic vul</content>
    <link href="https://about.gitlab.com/blog/gitlab-business-logic-security-analyzer/" rel="alternate"/>
    <category term="GitLab Blog" label="GitLab Blog"/>
    <published>2026-10-20T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1792521341/w2sdpy8hv2ucqxfejmn6.png" type="image/png" medium="image"/>
      <media:thumbnail url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1792521341/w2sdpy8hv2ucqxfejmn6.png"/>
    </media:group>
    <dc:creator>GitLab Blog</dc:creator>
    <link rel="enclosure" href="https://res.cloudinary.com/about-gitlab-com/image/upload/v1792521341/w2sdpy8hv2ucqxfejmn6.png" type="image/png" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/d6e5a7691dd6d91f</id>
    <title>Three developer tasks worth handing to an agent</title>
    <updated>2026-10-19T00:00:00+00:00</updated>
    <content>You already have an AI assistant. It completes your code, explains code you didn’t write, and maybe even drafts a whole feature while you sip your coffee. An agent on GitLab picks up where your editor stops. The AI in your editor only knows what's open in your editor. It doesn't know that your merge request has been sitting in the queue for two days, or that your pipeline failed for the third time this week. Without your pipeline logs, it can’t offer a fix. GitLab Duo Agent Platform works within</content>
    <link href="https://about.gitlab.com/blog/three-developer-tasks-worth-handing-to-an-agent/" rel="alternate"/>
    <category term="GitLab Blog" label="GitLab Blog"/>
    <published>2026-10-19T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1772564423/mvuznp7fepbt6payidvm.png" type="image/png" medium="image"/>
      <media:thumbnail url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1772564423/mvuznp7fepbt6payidvm.png"/>
    </media:group>
    <dc:creator>GitLab Blog</dc:creator>
    <link rel="enclosure" href="https://res.cloudinary.com/about-gitlab-com/image/upload/v1772564423/mvuznp7fepbt6payidvm.png" type="image/png" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/dfefafb24ea7565a</id>
    <title>Building AI security in the open</title>
    <updated>2026-10-19T00:00:00+00:00</updated>
    <content>When code becomes abundant trust becomes scarce. That is the argument GitLab CEO Bill Staples made in his recent essay : AI is collapsing the cost of producing software, and everything around production, including context, verification, governance, and evidence, becomes proportionally more important. Both security and collaboration are key elements to producing trust. AI widens what has to be trusted to include the agents that now write software along with the software that gets written. That is</content>
    <link href="https://about.gitlab.com/blog/gitlab-joins-open-secure-ai-alliance/" rel="alternate"/>
    <category term="GitLab Blog" label="GitLab Blog"/>
    <published>2026-10-19T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1773866173/vte9qh8rriznvyclhkes.png" type="image/png" medium="image"/>
      <media:thumbnail url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1773866173/vte9qh8rriznvyclhkes.png"/>
    </media:group>
    <dc:creator>GitLab Blog</dc:creator>
    <link rel="enclosure" href="https://res.cloudinary.com/about-gitlab-com/image/upload/v1773866173/vte9qh8rriznvyclhkes.png" type="image/png" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/a30c423a9bea2c25</id>
    <title>GitLab Secrets Manager: Govern secrets like your code</title>
    <updated>2026-10-15T00:00:00+00:00</updated>
    <content>Credentials often start in an engineer's local dev environments, then get copied into unscoped CI/CD variables to keep pipelines running. Stored there as a raw value rather than a reference to a scoped secret, a signing key reaches every job in the pipeline — compromised or not. Standing up a standalone vault narrows that exposure but requires mirroring every change to project membership, protected branches, and production environments. When the vault falls out of sync, a pipeline breaks or an a</content>
    <link href="https://about.gitlab.com/blog/secrets-manager-ga/" rel="alternate"/>
    <category term="GitLab Blog" label="GitLab Blog"/>
    <published>2026-10-15T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1791993648/t2kod74bclspits5cc5o.png" type="image/png" medium="image"/>
      <media:thumbnail url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1791993648/t2kod74bclspits5cc5o.png"/>
    </media:group>
    <dc:creator>GitLab Blog</dc:creator>
    <link rel="enclosure" href="https://res.cloudinary.com/about-gitlab-com/image/upload/v1791993648/t2kod74bclspits5cc5o.png" type="image/png" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/352abd561e929b70</id>
    <title>Get every merge request in front of the right reviewer, faster</title>
    <updated>2026-10-15T00:00:00+00:00</updated>
    <content>The code is written. Now who reviews it? The volume of code has never been greater, but delivery hasn’t kept pace. At Meta, code changes on internal platforms grew 220% year over year, while changes that reached users as new features grew only 36% ( Reuters , August 2026). Every one of those changes has to clear review before it reaches users. Automated review absorbs much of that load. Code Review Flow in GitLab Duo Agent Platform reviews merge requests as they arrive, follows custom review ins</content>
    <link href="https://about.gitlab.com/blog/recommend-reviewers-flow/" rel="alternate"/>
    <category term="GitLab Blog" label="GitLab Blog"/>
    <published>2026-10-15T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1791993839/e89thgfijypqjcbouhr4.png" type="image/png" medium="image"/>
      <media:thumbnail url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1791993839/e89thgfijypqjcbouhr4.png"/>
    </media:group>
    <dc:creator>GitLab Blog</dc:creator>
    <link rel="enclosure" href="https://res.cloudinary.com/about-gitlab-com/image/upload/v1791993839/e89thgfijypqjcbouhr4.png" type="image/png" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/f8513276a8cd30a2</id>
    <title>Connect your agents to your software lifecycle with the GitLab MCP server</title>
    <updated>2026-10-15T00:00:00+00:00</updated>
    <content>Agents are working across your team's software development lifecycle, but most still operate as separate tools, leaving the context, handoffs, and permissions for your team to stitch together. When your agents use APIs for these disparate tools, they often guess at endpoints and use up their context window on extra calls. The GitLab MCP server, now generally available with GitLab 19.5 , connects your team’s external agents to your entire software lifecycle — from planning through production. The</content>
    <link href="https://about.gitlab.com/blog/mcp-server-ga/" rel="alternate"/>
    <category term="GitLab Blog" label="GitLab Blog"/>
    <published>2026-10-15T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1791993648/t2kod74bclspits5cc5o.png" type="image/png" medium="image"/>
      <media:thumbnail url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1791993648/t2kod74bclspits5cc5o.png"/>
    </media:group>
    <dc:creator>GitLab Blog</dc:creator>
    <link rel="enclosure" href="https://res.cloudinary.com/about-gitlab-com/image/upload/v1791993648/t2kod74bclspits5cc5o.png" type="image/png" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/611fcf216bedebea</id>
    <title>GitLab 19.5 released</title>
    <updated>2026-10-15T00:00:00+00:00</updated>
    <content>GitLab 19.5 released</content>
    <link href="https://docs.gitlab.com/releases/19/gitlab-19-5-released/" rel="alternate"/>
    <category term="GitLab Blog" label="GitLab Blog"/>
    <published>2026-10-15T00:00:00+00:00</published>
    <dc:creator>GitLab Blog</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/aeb00c4801f5609b</id>
    <title>Unblock agentic software delivery with governed code review</title>
    <updated>2026-10-15T00:00:00+00:00</updated>
    <content>AI agents have changed how much code a team can produce in a day. Review queues haven’t kept up, and delivery stalls while changes wait for a closer look. The usual workarounds (reminders, reviewer rotations, assigning a team) buy a little time and then burn people out. Client-side review with AI helps the author by catching issues as the code is being written, before a merge request even opens. But it only goes so far. A review that only checks quality still leaves the organization without enfo</content>
    <link href="https://about.gitlab.com/blog/gitlab-code-review/" rel="alternate"/>
    <category term="GitLab Blog" label="GitLab Blog"/>
    <published>2026-10-15T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1792112882/t9x60iuneg6enpu55lp3.png" type="image/png" medium="image"/>
      <media:thumbnail url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1792112882/t9x60iuneg6enpu55lp3.png"/>
    </media:group>
    <dc:creator>GitLab Blog</dc:creator>
    <link rel="enclosure" href="https://res.cloudinary.com/about-gitlab-com/image/upload/v1792112882/t9x60iuneg6enpu55lp3.png" type="image/png" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/6ae41511603e6d71</id>
    <title>Forgejo v17.0 is available</title>
    <updated>2026-10-15T00:00:00+00:00</updated>
    <content>Forgejo v17.0 is available. Repository funding links are supported. Repositories can be migrated from Bitbucket Data Center. LFS support is revamped. Job summaries from Forgejo Actions jobs are displayed.</content>
    <link href="https://forgejo.org/2026-10-release-v17-0/" rel="alternate"/>
    <category term="Forgejo" label="Forgejo"/>
    <published>2026-10-15T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" medium="image"/>
      <media:thumbnail url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp"/>
    </media:group>
    <dc:creator>Forgejo</dc:creator>
    <link rel="enclosure" href="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/564f65e7088c1a54</id>
    <title>GitLab 19.5 release notes</title>
    <updated>2026-10-15T00:00:00+00:00</updated>
    <content>On October 15, 2026, GitLab 19.5 was released with the following features. We are excited to recognize Dhairya , a Level 3 contributor,
as this month’s Notable Contributor ! Dhairya contributed to offline transfer and Organizations support for import,
so that groups, projects, and their memberships can move between GitLab instances. Primary features GitLab MCP server is generally available Tier: Free, Premium, Ultimate Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated Links: Documentat</content>
    <link href="https://docs-review-mr-2788.gitlab-marketing.workers.dev/releases/19/gitlab-19-5-released/" rel="alternate"/>
    <category term="GitLab Releases" label="GitLab Releases"/>
    <published>2026-10-15T00:00:00+00:00</published>
    <dc:creator>GitLab Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/607961e055136a98</id>
    <title>Gemini 4 Argon on GitLab: Built for long-running agentic work</title>
    <updated>2026-10-14T00:00:00+00:00</updated>
    <content>As AI models take on longer, multi-step work, the challenge is putting that power to use across the software lifecycle without adding risk or cost. Teams need to be able to move faster, within enterprise controls and guardrails. Google's Gemini 4 Argon, now available on GitLab Duo Agent Platform , was built for that kind of work. With Argon, your team can delegate long, multi-step actions and receive outputs for review. In GitLab's internal evaluation, Gemini 4 Argon completed 93.3% of GitLab’s </content>
    <link href="https://about.gitlab.com/blog/gitlab-google-gemini-argon/" rel="alternate"/>
    <category term="GitLab Blog" label="GitLab Blog"/>
    <published>2026-10-14T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1773856365/gsx2c0vqlswox3ldmq88.jpg" type="image/jpeg" medium="image"/>
      <media:thumbnail url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1773856365/gsx2c0vqlswox3ldmq88.jpg"/>
    </media:group>
    <dc:creator>GitLab Blog</dc:creator>
    <link rel="enclosure" href="https://res.cloudinary.com/about-gitlab-com/image/upload/v1773856365/gsx2c0vqlswox3ldmq88.jpg" type="image/jpeg" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/4fc5fc94eac56ece</id>
    <title>Make every AI credit count: See, cap, and reduce agent spend</title>
    <updated>2026-10-13T00:00:00+00:00</updated>
    <content>Costs multiply with every task you hand to an agent. Each task consumes tokens and credits, and as agents spread across your teams and automations, consumption can grow faster than usage. If you run the platform, you own that growth, including which teams and workflows drive it and whether the usage ships work. At GitLab Transcend , we introduced the governed software factory , our architecture for agentic software engineering, and new capabilities in GitLab Duo Agent Platform that bring that gr</content>
    <link href="https://about.gitlab.com/blog/make-every-ai-credit-count/" rel="alternate"/>
    <category term="GitLab Blog" label="GitLab Blog"/>
    <published>2026-10-13T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1791898112/orfryk8astyh236ubwoi.png" type="image/png" medium="image"/>
      <media:thumbnail url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1791898112/orfryk8astyh236ubwoi.png"/>
    </media:group>
    <dc:creator>GitLab Blog</dc:creator>
    <link rel="enclosure" href="https://res.cloudinary.com/about-gitlab-com/image/upload/v1791898112/orfryk8astyh236ubwoi.png" type="image/png" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/95fa501361d061fa</id>
    <title>GitLab's agent orchestration eliminates the wait between development stages</title>
    <updated>2026-10-13T00:00:00+00:00</updated>
    <content>AI coding tools have changed how fast software gets written, but not how fast it ships. As code generation accelerates, the bottleneck moves downstream into verify, review, and ship. Those stages still run on human time. While agents write fixes in minutes, delivery slows on constant wait times and manual handoffs. Reviewer signoffs, pipeline alerts, scan triage, and step-by-step prompting are examples of obstacles DevOps teams face in maintaining on-time delivery. At GitLab Transcend , we annou</content>
    <link href="https://about.gitlab.com/blog/gitlab-agent-orchestration/" rel="alternate"/>
    <category term="GitLab Blog" label="GitLab Blog"/>
    <published>2026-10-13T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1791553685/v27u5ffzcw3l5qzx8bxs.png" type="image/png" medium="image"/>
      <media:thumbnail url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1791553685/v27u5ffzcw3l5qzx8bxs.png"/>
    </media:group>
    <dc:creator>GitLab Blog</dc:creator>
    <link rel="enclosure" href="https://res.cloudinary.com/about-gitlab-com/image/upload/v1791553685/v27u5ffzcw3l5qzx8bxs.png" type="image/png" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/c6838096b4fe80b0</id>
    <title>Scaling Git for the agentic software factory</title>
    <updated>2026-10-13T00:00:00+00:00</updated>
    <content>AI agents are fundamentally changing the economics of software development. As the cost of producing code falls, the volume of changes moving through the software factory is accelerating beyond what infrastructure designed for human developers was built to handle. GitLab anticipated this shift and began developing next-generation source code management (SCM) to support thousands of concurrent agents working against large repositories. In June, we announced next-gen SCM at GitLab Transcend, joine</content>
    <link href="https://about.gitlab.com/blog/scaling-git-for-the-agentic-software-factory/" rel="alternate"/>
    <category term="GitLab Blog" label="GitLab Blog"/>
    <published>2026-10-13T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1785336708/ww4mlighwlvvzgnmbe6w.png" type="image/png" medium="image"/>
      <media:thumbnail url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1785336708/ww4mlighwlvvzgnmbe6w.png"/>
    </media:group>
    <dc:creator>GitLab Blog</dc:creator>
    <link rel="enclosure" href="https://res.cloudinary.com/about-gitlab-com/image/upload/v1785336708/ww4mlighwlvvzgnmbe6w.png" type="image/png" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/94ad5e1339ecd5b0</id>
    <title>GitLab Critical Patch Release: 19.4.2, 19.3.4, 19.2.8</title>
    <updated>2026-10-12T00:00:00+00:00</updated>
    <content>GitLab Critical Patch Release: 19.4.2, 19.3.4, 19.2.8</content>
    <link href="https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-4-2-released/" rel="alternate"/>
    <category term="GitLab Blog" label="GitLab Blog"/>
    <published>2026-10-12T00:00:00+00:00</published>
    <dc:creator>GitLab Blog</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/3dfdc28276dadb69</id>
    <title>GitLab Critical Patch Release: 19.4.2, 19.3.5, 19.2.8</title>
    <updated>2026-10-12T00:00:00+00:00</updated>
    <content>On October 12, 2026, we released versions 19.4.2, 19.3.5, 19.2.8 for GitLab Community Edition (CE) and Enterprise Edition (EE). 19.3.4 had a bug that affected merge request pages when the Ona integration was enabled. This is fixed in 19.3.5. These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to
one of these versions immediately. GitLab.com is already running the patched version.
All GitLab Dedicated tenants we</content>
    <link href="https://docs-review-mr-2788.gitlab-marketing.workers.dev/releases/patches/patch-release-gitlab-19-4-2-released/" rel="alternate"/>
    <category term="GitLab Patch Releases" label="GitLab Patch Releases"/>
    <published>2026-10-12T00:00:00+00:00</published>
    <dc:creator>GitLab Patch Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/f69aad36783083d9</id>
    <title>Track organization-wide security risk in one dashboard</title>
    <updated>2026-10-08T00:00:00+00:00</updated>
    <content>If you run application security across more than one top-level group, getting a single organization-wide view of your risk has meant manually pulling together data. That is operational work rebuilt in spreadsheets and one-off scripts every time someone asks. This manual work is easy to get wrong, and is often out of date the moment it is published. Every hour spent assembling that view is an hour your security team is not spending on strategic work to drive down risk. With GitLab 19.4, the secur</content>
    <link href="https://about.gitlab.com/blog/security-risk-in-one-dashboard/" rel="alternate"/>
    <category term="GitLab Blog" label="GitLab Blog"/>
    <published>2026-10-08T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1790167851/bujr5fgc20p2uf8uag1z.png" type="image/png" medium="image"/>
      <media:thumbnail url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1790167851/bujr5fgc20p2uf8uag1z.png"/>
    </media:group>
    <dc:creator>GitLab Blog</dc:creator>
    <link rel="enclosure" href="https://res.cloudinary.com/about-gitlab-com/image/upload/v1790167851/bujr5fgc20p2uf8uag1z.png" type="image/png" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/ae58f50f0fa632bd</id>
    <title>Migrate your site to the new git-pages backed Codeberg Pages now. We're sunsetting Codeberg Pages v2</title>
    <updated>2026-10-06T22:00:00+00:00</updated>
    <content>For many years, Codeberg Pages v2, our in-house solution, served as a way for hosting project pages through your_codeberg_username .codeberg.page or custom domains. This project has been unmaintained for a longer time now, and we already have git-pages as a replacement to power Codeberg Pages. A lot of users …</content>
    <link href="https://blog.codeberg.org/migrate-your-site-to-the-new-git-pages-backed-codeberg-pages-now-were-sunsetting-codeberg-pages-v2.html" rel="alternate"/>
    <category term="Codeberg" label="Codeberg"/>
    <published>2026-10-06T22:00:00+00:00</published>
    <dc:creator>Codeberg</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/c818c9d031f090d9</id>
    <title>GitLab Transcend: Speed you can trust, all the way to production</title>
    <updated>2026-10-06T00:00:00+00:00</updated>
    <content>At Transcend, we made over a dozen announcements across all four layers of our architecture for agentic software engineering: agent orchestration, data and context, DevOps workflows, and governance and security. Watch the replay , or read on for what shipped and how to turn on the new capabilities. At a glance What we launched Release status What it does Goal-driven flows ( /goal ) GA this month Carry a change through review, tests, scans, and approvals without waiting between stages of the soft</content>
    <link href="https://about.gitlab.com/blog/transcend-india-announcements/" rel="alternate"/>
    <category term="GitLab Blog" label="GitLab Blog"/>
    <published>2026-10-06T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1791198675/kmajkudog4fj3xc6qfyb.png" type="image/png" medium="image"/>
      <media:thumbnail url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1791198675/kmajkudog4fj3xc6qfyb.png"/>
    </media:group>
    <dc:creator>GitLab Blog</dc:creator>
    <link rel="enclosure" href="https://res.cloudinary.com/about-gitlab-com/image/upload/v1791198675/kmajkudog4fj3xc6qfyb.png" type="image/png" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/9a27a541d61e72ee</id>
    <title>Dependency Firewall: Block risky packages before the build</title>
    <updated>2026-10-06T00:00:00+00:00</updated>
    <content>Attackers disguise malicious packages as ones you trust. In June 2026, GitLab researchers found five malicious PyPI packages , four of them typosquats of Flask, Requests, and NumPy, that run at install time and steal CI/CD credentials. Additionally, AI coding agents now add open source dependencies on their own, often unreviewed, so developers don't have oversight into what packages may contaminate your build. Once a malicious or vulnerable package enters your build, its code may run with the sa</content>
    <link href="https://about.gitlab.com/blog/transcend-dependency-firewall/" rel="alternate"/>
    <category term="GitLab Blog" label="GitLab Blog"/>
    <published>2026-10-06T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1791198870/smilnde9xskkyon7rzyn.jpg" type="image/jpeg" medium="image"/>
      <media:thumbnail url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1791198870/smilnde9xskkyon7rzyn.jpg"/>
    </media:group>
    <dc:creator>GitLab Blog</dc:creator>
    <link rel="enclosure" href="https://res.cloudinary.com/about-gitlab-com/image/upload/v1791198870/smilnde9xskkyon7rzyn.jpg" type="image/jpeg" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/088dac51f093abeb</id>
    <title>Every artifact your teams ship, assembled right the first time</title>
    <updated>2026-10-06T00:00:00+00:00</updated>
    <content>Every software build is assembled from open source packages, base images, and libraries, with your code on top. When one of those components is missing or has drifted, the build fails. At agent speed, those failures multiply, and no team can clear them as manual exceptions. Project-by-project registry sprawl makes it worse because retention rules, storage limits, and publish access all live separately inside each project. Project-level design works when a person sets up each registry by hand, bu</content>
    <link href="https://about.gitlab.com/blog/transcend-artifact-central/" rel="alternate"/>
    <category term="GitLab Blog" label="GitLab Blog"/>
    <published>2026-10-06T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1791239267/zfd9zisjm0gqkj5relb9.png" type="image/png" medium="image"/>
      <media:thumbnail url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1791239267/zfd9zisjm0gqkj5relb9.png"/>
    </media:group>
    <dc:creator>GitLab Blog</dc:creator>
    <link rel="enclosure" href="https://res.cloudinary.com/about-gitlab-com/image/upload/v1791239267/zfd9zisjm0gqkj5relb9.png" type="image/png" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/7156c898b56225b1</id>
    <title>Two front doors: Module-level access in a Django GRC app</title>
    <updated>2026-10-05T00:00:00+00:00</updated>
    <content>GitLab's engineering team builds a lot of our own internal tooling, but one platform in particular forced us to rethink how we handle authorization: our internal GRC tool that serves two very different customer bases under one roof — our Security Compliance team and our Internal Audit team. If you're building or maintaining an internal Django tool that's starting to serve more than one audience — different teams, different data classification levels, different data that shouldn't cross streams —</content>
    <link href="https://about.gitlab.com/blog/module-level-access-in-a-django-grc-app/" rel="alternate"/>
    <category term="GitLab Blog" label="GitLab Blog"/>
    <published>2026-10-05T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1750097663/Blog/Hero%20Images/Blog/Hero%20Images/Workflow%201800x945_2gQoQIbY9NvjLFpXtsxtXy_1750097663612.png" type="image/png" medium="image"/>
      <media:thumbnail url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1750097663/Blog/Hero%20Images/Blog/Hero%20Images/Workflow%201800x945_2gQoQIbY9NvjLFpXtsxtXy_1750097663612.png"/>
    </media:group>
    <dc:creator>GitLab Blog</dc:creator>
    <link rel="enclosure" href="https://res.cloudinary.com/about-gitlab-com/image/upload/v1750097663/Blog/Hero%20Images/Blog/Hero%20Images/Workflow%201800x945_2gQoQIbY9NvjLFpXtsxtXy_1750097663612.png" type="image/png" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/415782a46f992c00</id>
    <title>DeepSeek-Reasonix: How a poisoned config can hijack an AI coding agent</title>
    <updated>2026-10-02T00:00:00+00:00</updated>
    <content>GitLab's Threat Research Group discovered a command execution vulnerability ( GHSA-grg2-7gc6-36m6 , CVE-2026-102437 ) in DeepSeek-Reasonix Studio, a desktop git client designed for developers pairing with AI coding assistants. The flaw, called ConfigPoisoning, could allow attacker-supplied code to execute when a developer views a file's diff. To address this vulnerability, you should update to DeepSeek-Reasonix Studio 2.21.0 or DeepSeek Reasonix npm 1.39.3. This is not an isolated DeepSeek-Reaso</content>
    <link href="https://about.gitlab.com/blog/deepseek-reasonix-vulnerability-discovered/" rel="alternate"/>
    <category term="GitLab Blog" label="GitLab Blog"/>
    <published>2026-10-02T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1782237704/cj50chkvprjthczevmog.png" type="image/png" medium="image"/>
      <media:thumbnail url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1782237704/cj50chkvprjthczevmog.png"/>
    </media:group>
    <dc:creator>GitLab Blog</dc:creator>
    <link rel="enclosure" href="https://res.cloudinary.com/about-gitlab-com/image/upload/v1782237704/cj50chkvprjthczevmog.png" type="image/png" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/2243b349d3b95723</id>
    <title>GitLab AI Gateway Critical Patch Release: 19.2.4, 19.3.2, and 19.4.1</title>
    <updated>2026-10-02T00:00:00+00:00</updated>
    <content>We have released versions 19.2.4, 19.3.2, and 19.4.1 of the GitLab AI Gateway. These versions contain a critical security fix for GitLab Self-Hosted AI Gateway, and we strongly recommend that all GitLab Self-Managed customers with GitLab Self-Hosted AI Gateway installations update to one of these versions immediately. We have conducted targeted outreach to Self-Hosted AI Gateway customers prior to this release post with this guidance. A fix has already been deployed for GitLab-hosted AI Gateways</content>
    <link href="https://docs.gitlab.com/releases/patches/other-patches/patch-release-gitlab-ai-gateway-19-4-1-released/" rel="alternate"/>
    <category term="GitLab Patch Releases" label="GitLab Patch Releases"/>
    <published>2026-10-02T00:00:00+00:00</published>
    <dc:creator>GitLab Patch Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/215f7c420e12bfd3</id>
    <title>GitLab and Claude Code: Fast, compliant AI</title>
    <updated>2026-09-29T00:00:00+00:00</updated>
    <content>Government agencies are feeling twin pressures: While the U.S. Office of Management and Budget (OMB) is urging you to deploy AI faster, the U.S. Government Accountability Office (GAO) wants guardrails in place before that happens. To accelerate AI coding, many agencies are turning to AI coding assistants like Anthropic's Claude Code. But what about guardrails? GitLab Duo Agent Platform can govern your entire software development lifecycle, regardless of which model creates your code. The need fo</content>
    <link href="https://about.gitlab.com/blog/gitlab-and-claude-code-fast-compliant-ai/" rel="alternate"/>
    <category term="GitLab Blog" label="GitLab Blog"/>
    <published>2026-09-29T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1789480051/fbgjewuov2brmwynv1pj.png" type="image/png" medium="image"/>
      <media:thumbnail url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1789480051/fbgjewuov2brmwynv1pj.png"/>
    </media:group>
    <dc:creator>GitLab Blog</dc:creator>
    <link rel="enclosure" href="https://res.cloudinary.com/about-gitlab-com/image/upload/v1789480051/fbgjewuov2brmwynv1pj.png" type="image/png" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/4a984966a903e12d</id>
    <title>What's new in Git 2.56.0?</title>
    <updated>2026-09-28T00:00:00+00:00</updated>
    <content>The Git project recently released Git 2.56.0 . Let's look at some of the highlights of the release, including contributions from the Git team at GitLab. What's covered: Git Merge 2026 and schedule for Git 3.0 git-history(1) learns drop git-branch(1) learns to delete merged branches git-refs(1) learns to modify refs Google Summer of Code 2026 Linearizing history with git-replay(1) Making the object database pluggable Git Merge 2026 and schedule for Git 3.0 This release cycle coincided with Git Me</content>
    <link href="https://about.gitlab.com/blog/whats-new-in-git-2-56-0/" rel="alternate"/>
    <category term="GitLab Blog" label="GitLab Blog"/>
    <published>2026-09-28T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1782732487/ztwgrvlolpifo01vj8qc.png" type="image/png" medium="image"/>
      <media:thumbnail url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1782732487/ztwgrvlolpifo01vj8qc.png"/>
    </media:group>
    <dc:creator>GitLab Blog</dc:creator>
    <link rel="enclosure" href="https://res.cloudinary.com/about-gitlab-com/image/upload/v1782732487/ztwgrvlolpifo01vj8qc.png" type="image/png" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/6d64a5a55a31db5f</id>
    <title>GitLab Critical Patch Release: 19.4.1, 19.3.3, 19.2.7</title>
    <updated>2026-09-23T00:00:00+00:00</updated>
    <content>On September 23, 2026, we released versions 19.4.1, 19.3.3, 19.2.7 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to
one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action. GitLab releases fixes for vulnerabilities in patch releases. There are two types of patc</content>
    <link href="https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-4-1-released/" rel="alternate"/>
    <category term="GitLab Patch Releases" label="GitLab Patch Releases"/>
    <published>2026-09-23T00:00:00+00:00</published>
    <dc:creator>GitLab Patch Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/65a66e58d293dac0</id>
    <title>GitLab Critical Patch Release: 19.0.9, 18.11.12</title>
    <updated>2026-09-23T00:00:00+00:00</updated>
    <content>On September 23, 2026, we released versions 19.0.9 and 18.11.12 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions backport the fixes for two critical vulnerabilities, CVE-2026-85706 and CVE-2026-87719, that were originally patched in 19.3.2, 19.2.6, and 19.1.8 on September 10, 2026. These backports were made available outside of our standard maintenance policy so that self-managed administrators running 18.11 and 19.0 can apply the fixes without first completing a ver</content>
    <link href="https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-0-9-released/" rel="alternate"/>
    <category term="GitLab Patch Releases" label="GitLab Patch Releases"/>
    <published>2026-09-23T00:00:00+00:00</published>
    <dc:creator>GitLab Patch Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/091165d5e6a45216</id>
    <title>How to design GitLab for enterprise scale</title>
    <updated>2026-09-22T00:00:00+00:00</updated>
    <content>At enterprise scale, even small architecture choices can have outsized consequences. A deployment that works for a handful of teams can become a constraint once thousands of developers, repositories, and pipelines depend on it. That makes each decision made before rollout especially consequential. For example, your: Deployment model defines what your team must operate Runner strategy shapes how CI/CD workloads execute and stay isolated, as well as how much operational load falls on your platform</content>
    <link href="https://about.gitlab.com/blog/how-to-design-gitlab-for-enterprise-scale/" rel="alternate"/>
    <category term="GitLab Blog" label="GitLab Blog"/>
    <published>2026-09-22T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1772058602/epl3sinfezlzxnppxak6.png" type="image/png" medium="image"/>
      <media:thumbnail url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1772058602/epl3sinfezlzxnppxak6.png"/>
    </media:group>
    <dc:creator>GitLab Blog</dc:creator>
    <link rel="enclosure" href="https://res.cloudinary.com/about-gitlab-com/image/upload/v1772058602/epl3sinfezlzxnppxak6.png" type="image/png" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/74703454eb25b6ac</id>
    <title>How GitLab reduced code-per-agentic-flow ratio by 45%</title>
    <updated>2026-09-22T00:00:00+00:00</updated>
    <content>GitLab Duo Agent Platform orchestrates and automates complex tasks through agentic flows. A key part of the platform is the Flow Registry, a declarative configuration framework, built from reusable components, that compiles YAML into fully functional LangGraph flows. By using Flow Registry, agent builders — both our GitLab engineers and our customers  can use declarative YAML configurations instead of repetitive, ad-hoc Python implementations. Flow Registry turns bespoke state management and age</content>
    <link href="https://about.gitlab.com/blog/how-gitlab-reduced-code-per-agentic-flow-ratio/" rel="alternate"/>
    <category term="GitLab Blog" label="GitLab Blog"/>
    <published>2026-09-22T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1774465167/n5hlvrsrheadeccyr1oz.png" type="image/png" medium="image"/>
      <media:thumbnail url="https://res.cloudinary.com/about-gitlab-com/image/upload/v1774465167/n5hlvrsrheadeccyr1oz.png"/>
    </media:group>
    <dc:creator>GitLab Blog</dc:creator>
    <link rel="enclosure" href="https://res.cloudinary.com/about-gitlab-com/image/upload/v1774465167/n5hlvrsrheadeccyr1oz.png" type="image/png" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/4e7837fa3361c634</id>
    <title>GitLab 19.4 release notes</title>
    <updated>2026-09-17T00:00:00+00:00</updated>
    <content>On September 17, 2026, GitLab 19.4 was released with the following features. We are excited to recognize Jimmy , a Level 4 contributor,
as this month’s Notable Contributor ! Jimmy contributed across the GitLab codebase, client-go , and the Terraform
provider to ensure that tokens, service accounts, and push mirrors can be
managed end to end through infrastructure as code. Primary features Governance for GitLab MCP server tools Tier: Free, Premium, Ultimate Offering: GitLab.com, GitLab Self-Manag</content>
    <link href="https://docs.gitlab.com/releases/19/gitlab-19-4-released/" rel="alternate"/>
    <category term="GitLab Releases" label="GitLab Releases"/>
    <published>2026-09-17T00:00:00+00:00</published>
    <dc:creator>GitLab Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/d90b22bbe29c1057</id>
    <title>GitLab Critical Patch Release: 19.3.2, 19.2.6, 19.1.8</title>
    <updated>2026-09-10T00:00:00+00:00</updated>
    <content>Update : On September 23, 2026, we backported fixes for CVE-2026-85706 and CVE-2026-87719 to versions 19.0.9 and 18.11.12 of GitLab Community Edition (CE) and Enterprise Edition (EE). Self-managed GitLab administrators running older versions of GitLab CE and EE can now upgrade to these versions to apply these security fixes. On September 10, 2026, we released versions 19.3.2, 19.2.6, 19.1.8 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and se</content>
    <link href="https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-3-2-released/" rel="alternate"/>
    <category term="GitLab Patch Releases" label="GitLab Patch Releases"/>
    <published>2026-09-10T00:00:00+00:00</published>
    <dc:creator>GitLab Patch Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/9f530a665aeaf7e0</id>
    <title>Forgejo Runner v13.1.0 is available</title>
    <updated>2026-09-03T00:00:00+00:00</updated>
    <content>Forgejo Runner v13.1.0 is available. An experimental plugin capability allows Forgejo Runner to support user-developed pluggable execution environments.</content>
    <link href="https://forgejo.org/2026-09-runner-release-v131/" rel="alternate"/>
    <category term="Forgejo" label="Forgejo"/>
    <published>2026-09-03T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" medium="image"/>
      <media:thumbnail url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp"/>
    </media:group>
    <dc:creator>Forgejo</dc:creator>
    <link rel="enclosure" href="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/d4188021da97328a</id>
    <title>GitLab Patch Release: 19.3.1, 19.2.5, 19.1.7</title>
    <updated>2026-08-26T00:00:00+00:00</updated>
    <content>On August 26, 2026, we released versions 19.3.1, 19.2.5, 19.1.7 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to
one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action. GitLab releases fixes for vulnerabilities in patch releases. There are two types of patch r</content>
    <link href="https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-3-1-released/" rel="alternate"/>
    <category term="GitLab Patch Releases" label="GitLab Patch Releases"/>
    <published>2026-08-26T00:00:00+00:00</published>
    <dc:creator>GitLab Patch Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/a57792a5e528568a</id>
    <title>GitLab 19.3 release notes</title>
    <updated>2026-08-20T00:00:00+00:00</updated>
    <content>On August 20, 2026, GitLab 19.3 was released with the following features. We are excited to recognize gkepas as this month’s Notable Contributor ! Giannis has made sustained contributions across the GitLab codebase, the contributor
platform, client-go , the Terraform provider, and GitLab Orbit.
He is also an active translator and a member of the GitLab Community Discord. Primary features Flow Creator foundational agent Tier: Premium, Ultimate Offering: GitLab.com, GitLab Self-Managed, GitLab Ded</content>
    <link href="https://docs.gitlab.com/releases/19/gitlab-19-3-released/" rel="alternate"/>
    <category term="GitLab Releases" label="GitLab Releases"/>
    <published>2026-08-20T00:00:00+00:00</published>
    <dc:creator>GitLab Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/9e5c594a9babe170</id>
    <title>GitLab Patch Release: 19.2.2, 19.1.4, 19.0.6</title>
    <updated>2026-08-12T00:00:00+00:00</updated>
    <content>On August 12, 2026, we released versions 19.2.2, 19.1.4, 19.0.6 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to
one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action. GitLab releases fixes for vulnerabilities in patch releases. There are two types of patch r</content>
    <link href="https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-2-2-released/" rel="alternate"/>
    <category term="GitLab Patch Releases" label="GitLab Patch Releases"/>
    <published>2026-08-12T00:00:00+00:00</published>
    <dc:creator>GitLab Patch Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/710668cb506b7e5f</id>
    <title>GitLab Patch Release: 18.11.9</title>
    <updated>2026-08-06T00:00:00+00:00</updated>
    <content>On August 6, 2026, we released versions 18.11.9 for GitLab Community Edition and Enterprise Edition. These versions resolve a number of regressions and bugs. This patch release does not include any security fixes. GitLab Community Edition and Enterprise Edition 18.11.9 We have pulled the omnibus install of 18.11.8 and replaced it with 18.11.9. A bug was found in the deprecation code that enabled Mattermost incorrectly. If you have a local cache of our omnibus package, you will want to remove 18.</content>
    <link href="https://docs.gitlab.com/releases/patches/patch-release-gitlab-18-11-9-released/" rel="alternate"/>
    <category term="GitLab Patch Releases" label="GitLab Patch Releases"/>
    <published>2026-08-06T00:00:00+00:00</published>
    <dc:creator>GitLab Patch Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/f0ba371aaa5a4f0b</id>
    <title>GitLab Patch Release: 18.11.8</title>
    <updated>2026-08-05T00:00:00+00:00</updated>
    <content>On August 5, 2026, we released versions 18.11.8 for GitLab Community Edition and Enterprise Edition. These versions resolve a number of regressions and bugs. This patch release does not include any security fixes. GitLab Community Edition and Enterprise Edition 18.11.8 Update gitlab-logger to v4.0.1 (18-11-stable) Backport of ‘Keep virtual registry settings toggle visible when disabled’ into 18.11 Backport of “Fix blob preview diff hiding blank added lines” Backport of ‘Backfill duo_secret_detec</content>
    <link href="https://docs.gitlab.com/releases/patches/patch-release-gitlab-18-11-8-released/" rel="alternate"/>
    <category term="GitLab Patch Releases" label="GitLab Patch Releases"/>
    <published>2026-08-05T00:00:00+00:00</published>
    <dc:creator>GitLab Patch Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/4fffbef31a40a838</id>
    <title>Forgejo Runner v13.0.0 is available</title>
    <updated>2026-08-03T00:00:00+00:00</updated>
    <content>Forgejo Runner v13.0.0 is available. Breaking changes have been made to improve security and predictability of Forgejo Actions.</content>
    <link href="https://forgejo.org/2026-08-runner-release-v13/" rel="alternate"/>
    <category term="Forgejo" label="Forgejo"/>
    <published>2026-08-03T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" medium="image"/>
      <media:thumbnail url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp"/>
    </media:group>
    <dc:creator>Forgejo</dc:creator>
    <link rel="enclosure" href="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/7089efae6f50cb16</id>
    <title>GitLab Patch Release: 19.2.1, 19.1.3, 19.0.5</title>
    <updated>2026-07-29T00:00:00+00:00</updated>
    <content>On July 29, 2026, we released versions 19.2.1, 19.1.3, 19.0.5 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to
one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action. GitLab releases fixes for vulnerabilities in patch releases. There are two types of patch rel</content>
    <link href="https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-2-1-released/" rel="alternate"/>
    <category term="GitLab Patch Releases" label="GitLab Patch Releases"/>
    <published>2026-07-29T00:00:00+00:00</published>
    <dc:creator>GitLab Patch Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/8fd767c08639ff59</id>
    <title>Protecting our FLOSS commons from LLMs</title>
    <updated>2026-07-22T22:00:00+00:00</updated>
    <content>In Brief: Two motions regarding "artificial intelligence" and Large Language Models (LLMs) were voted on among Codeberg e. V. members and passed. We are promising to not use any of your data to train LLM and explain what the planned Terms of Use change mean for 'vibe-coded' projects. We believe …</content>
    <link href="https://blog.codeberg.org/protecting-our-floss-commons-from-llms.html" rel="alternate"/>
    <category term="Codeberg" label="Codeberg"/>
    <published>2026-07-22T22:00:00+00:00</published>
    <dc:creator>Codeberg</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/e155fe6da103d102</id>
    <title>Forgejo v16.0 is available</title>
    <updated>2026-07-16T00:00:00+00:00</updated>
    <content>Forgejo v16.0 is available. Repository watch now has options. Authorized Integrations allow secret-less access to the API. Review comments can be placed on multiple lines of code. Improved security of pull mirrors.</content>
    <link href="https://forgejo.org/2026-07-release-v16-0/" rel="alternate"/>
    <category term="Forgejo" label="Forgejo"/>
    <published>2026-07-16T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" medium="image"/>
      <media:thumbnail url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp"/>
    </media:group>
    <dc:creator>Forgejo</dc:creator>
    <link rel="enclosure" href="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/64b1860e7707ef87</id>
    <title>GitLab 19.2 release notes</title>
    <updated>2026-07-16T00:00:00+00:00</updated>
    <content>On July 16, 2026, GitLab 19.2 was released with the following features. We are excited to recognize vivekshukl007 as this month’s Notable Contributor ! Vivek is a Senior Data Engineer at Emirates who made a high-impact contribution to add Scala language support to GitLab Orbit. This change improves the code graph capabilities for developers who work in Scala codebases. Primary features GitLab Duo CLI is now generally available Tier: Premium, Ultimate Offering: GitLab.com, GitLab Self-Managed, Gi</content>
    <link href="https://docs.gitlab.com/releases/19/gitlab-19-2-released/" rel="alternate"/>
    <category term="GitLab Releases" label="GitLab Releases"/>
    <published>2026-07-16T00:00:00+00:00</published>
    <dc:creator>GitLab Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/355bf0a6c39ce838</id>
    <title>GitLab Patch Release: 19.1.2, 19.0.4, 18.11.7</title>
    <updated>2026-07-08T00:00:00+00:00</updated>
    <content>On July 8, 2026, we released versions 19.1.2, 19.0.4, 18.11.7 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to
one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action. GitLab releases fixes for vulnerabilities in patch releases. There are two types of patch rel</content>
    <link href="https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-1-2-released/" rel="alternate"/>
    <category term="GitLab Patch Releases" label="GitLab Patch Releases"/>
    <published>2026-07-08T00:00:00+00:00</published>
    <dc:creator>GitLab Patch Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/b04e1cf7e355bac9</id>
    <title>GitLab patch release notes</title>
    <updated>2026-06-24T00:00:00+00:00</updated>
    <content>GitLab patch release notes</content>
    <link href="https://docs.gitlab.com/releases/patches/" rel="alternate"/>
    <category term="GitLab Patch Releases" label="GitLab Patch Releases"/>
    <published>2026-06-24T00:00:00+00:00</published>
    <dc:creator>GitLab Patch Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/343f7e3da957621a</id>
    <title>GitLab 19.1 release notes</title>
    <updated>2026-06-18T00:00:00+00:00</updated>
    <content>On June 18, 2026, GitLab 19.1 was released with the following features. We’d also like to announce this month’s Notable Contributor : Pishel65! We are excited to recognize Pishel65 , a Level 3 contributor with 19 merged MRs and 9 more open since joining in October 2025. Primary features Secret false positive detection with GitLab Duo Tier: Ultimate Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government Links: Documentation · Related Issue Secret false positi</content>
    <link href="https://docs-review-mr-2788.gitlab-marketing.workers.dev/releases/19/gitlab-19-1-released/" rel="alternate"/>
    <category term="GitLab Releases" label="GitLab Releases"/>
    <published>2026-06-18T00:00:00+00:00</published>
    <dc:creator>GitLab Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/197fc4fd6870d620</id>
    <title>GitLab Patch Release: 19.0.2, 18.11.5, 18.10.8</title>
    <updated>2026-06-10T00:00:00+00:00</updated>
    <content>On June 10, 2026, we released versions 19.0.2, 18.11.5, 18.10.8 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to
one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action. GitLab releases fixes for vulnerabilities in patch releases. There are two types of patch r</content>
    <link href="https://docs.gitlab.com/ja-jp/releases/patches/patch-release-gitlab-19-0-2-released/" rel="alternate"/>
    <category term="GitLab Patch Releases" label="GitLab Patch Releases"/>
    <published>2026-06-10T00:00:00+00:00</published>
    <dc:creator>GitLab Patch Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/c38b88638309f30b</id>
    <title>Forgejo monthly report - May 2026</title>
    <updated>2026-06-08T00:00:00+00:00</updated>
    <content>Forgejo v15 was released, along with security releases. The Forgejo Security Team responds to community concerns. The Forgejo Runner had multiple releases, the Forgejo Helm chart v17 was released and the Forgejo v16 release is progressing.</content>
    <link href="https://forgejo.org/2026-05-monthly-report/" rel="alternate"/>
    <category term="Forgejo" label="Forgejo"/>
    <published>2026-06-08T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" medium="image"/>
      <media:thumbnail url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp"/>
    </media:group>
    <dc:creator>Forgejo</dc:creator>
    <link rel="enclosure" href="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/3dfb6edc86bc8982</id>
    <title>GitLab Patch Release: 18.9.8, 18.8.10, 18.7.7, 18.6.8, 18.5.7</title>
    <updated>2026-05-27T00:00:00+00:00</updated>
    <content>Today, we are releasing versions 18.9.8, 18.8.10, 18.7.7, 18.6.8, and 18.5.7 for GitLab Community Edition and Enterprise Edition. These versions resolve a number of regressions and bugs. This patch release does not include any security fixes. This patch release addresses a regression introduced in GitLab 18.4 where issues appeared duplicated in Epic swimlane board views — showing under both their direct parent epic and the grandparent epic — even when no filter was applied. This caused boards to</content>
    <link href="https://docs.gitlab.com/releases/patches/patch-release-gitlab-18-9-8-released/" rel="alternate"/>
    <category term="GitLab Patch Releases" label="GitLab Patch Releases"/>
    <published>2026-05-27T00:00:00+00:00</published>
    <dc:creator>GitLab Patch Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/6ff08eafa9c98436</id>
    <title>GitLab Patch Release: 19.0.1, 18.11.4, 18.10.7</title>
    <updated>2026-05-27T00:00:00+00:00</updated>
    <content>On May 27, 2026, we released versions 19.0.1, 18.11.4, 18.10.7 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to
one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action. GitLab releases fixes for vulnerabilities in patch releases. There are two types of patch re</content>
    <link href="https://docs.gitlab.com/ja-jp/releases/patches/patch-release-gitlab-19-0-1-released/" rel="alternate"/>
    <category term="GitLab Patch Releases" label="GitLab Patch Releases"/>
    <published>2026-05-27T00:00:00+00:00</published>
    <dc:creator>GitLab Patch Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/81847cc1038de9c8</id>
    <title>GitLab 19.0 release notes</title>
    <updated>2026-05-21T00:00:00+00:00</updated>
    <content>On May 21, 2026, GitLab 19.0 was released with the following features. We’d also like to announce this month’s Notable Contributor :
Norman Debald! We are excited to recognize Norman , a Level 3 contributor
with more than 40 merged improvements across GitLab since joining in May 2022. Primary features Group-level custom review instructions for GitLab Duo Tier: Premium, Ultimate Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated Add-ons: GitLab Duo Enterprise Links: Documentation · Relat</content>
    <link href="https://docs.gitlab.com/releases/19/gitlab-19-0-released/" rel="alternate"/>
    <category term="GitLab Releases" label="GitLab Releases"/>
    <published>2026-05-21T00:00:00+00:00</published>
    <dc:creator>GitLab Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/913a7f2f8d94a937</id>
    <title>Codeberg's Budget of 2026</title>
    <updated>2026-05-14T22:00:00+00:00</updated>
    <content>Codeberg e.V. is entering its seventh year.
We have grown in projects and members but also in organizational structure and money. While Codeberg e.V. was spending only about 300 € in 2019, our budgeting has reached much higher amounts by now.
We are grateful for your donations and spend …</content>
    <link href="https://blog.codeberg.org/codebergs-budget-of-2026.html" rel="alternate"/>
    <category term="Codeberg" label="Codeberg"/>
    <published>2026-05-14T22:00:00+00:00</published>
    <dc:creator>Codeberg</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/733695834a76ac36</id>
    <title>GitLab Patch Release: 18.11.3, 18.10.6, 18.9.7</title>
    <updated>2026-05-13T00:00:00+00:00</updated>
    <content>On May 13, 2026, we released versions 18.11.3, 18.10.6, 18.9.7 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to
one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action. GitLab releases fixes for vulnerabilities in patch releases. There are two types of patch re</content>
    <link href="https://docs.gitlab.com/releases/patches/patch-release-gitlab-18-11-3-released/" rel="alternate"/>
    <category term="GitLab Patch Releases" label="GitLab Patch Releases"/>
    <published>2026-05-13T00:00:00+00:00</published>
    <dc:creator>GitLab Patch Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/99179620b26766e9</id>
    <title>GitLab Patch Release: 18.11.2, 18.10.5</title>
    <updated>2026-04-29T00:00:00+00:00</updated>
    <content>On April 29, 2026, we released versions 18.11.2 and 18.10.5 for GitLab Community Edition and Enterprise Edition. These out-of-band patch releases fix an observability gap to ensure we continue to meet our disaster recovery RTO/RPO commitments for our GitLab Dedicated customers. These versions also resolve a number of regressions and bugs. This patch release does not include any security fixes. GitLab Community Edition and Enterprise Edition 18.11.2 Revert “Merge branch ‘ia-refactor-role-permissi</content>
    <link href="https://docs.gitlab.com/releases/patches/patch-release-gitlab-18-11-2-released/" rel="alternate"/>
    <category term="GitLab Patch Releases" label="GitLab Patch Releases"/>
    <published>2026-04-29T00:00:00+00:00</published>
    <dc:creator>GitLab Patch Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/b8472a280df27e76</id>
    <title>GitLab Patch Release: 18.11.1, 18.10.4, 18.9.6</title>
    <updated>2026-04-22T00:00:00+00:00</updated>
    <content>On April 22, 2026, we released versions 18.11.1, 18.10.4, 18.9.6 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to
one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action. GitLab releases fixes for vulnerabilities in patch releases. There are two types of patch </content>
    <link href="https://docs.gitlab.com/releases/patches/patch-release-gitlab-18-11-1-released/" rel="alternate"/>
    <category term="GitLab Patch Releases" label="GitLab Patch Releases"/>
    <published>2026-04-22T00:00:00+00:00</published>
    <dc:creator>GitLab Patch Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/7abd9ada17611c18</id>
    <title>GitLab 18.11 release notes</title>
    <updated>2026-04-16T00:00:00+00:00</updated>
    <content>On April 16, 2026, GitLab 18.11 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor. This month’s Notable Contributor: Rinku C We are excited to recognize Rinku C , a Level 4 contributor with over 80 merged improvements across GitLab since joining in September 2025. Nominated by Arianna Haradon , Senior Fullstack Engineer on the Developer Relations team, this award celebrates his sustained and meaningful impa</content>
    <link href="https://docs.gitlab.com/releases/18/gitlab-18-11-released/" rel="alternate"/>
    <category term="GitLab Releases" label="GitLab Releases"/>
    <published>2026-04-16T00:00:00+00:00</published>
    <dc:creator>GitLab Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/1be280e0779af22e</id>
    <title>Forgejo v15.0 is available</title>
    <updated>2026-04-16T00:00:00+00:00</updated>
    <content>Forgejo v15.0 is available. Access tokens can now be restricted to specific repos. New containers are now auto-linked if possible. Responsiveness and accessibility of the UI were improved. Forgejo actions gained multiple new features. As an LTS version, it will be supported until 15 July 2027.</content>
    <link href="https://forgejo.org/2026-04-release-v15-0/" rel="alternate"/>
    <category term="Forgejo" label="Forgejo"/>
    <published>2026-04-16T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" medium="image"/>
      <media:thumbnail url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp"/>
    </media:group>
    <dc:creator>Forgejo</dc:creator>
    <link rel="enclosure" href="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/22c67bd1517a279b</id>
    <title>Forgejo monthly report - March 2026</title>
    <updated>2026-04-12T00:00:00+00:00</updated>
    <content>The Forgejo v15.0 branch has been cut and the release is scheduled for April 16. Security releases for Forgejo were published. The AI-Agreement was updated. code.forgejo.org is not a free public git hosting.</content>
    <link href="https://forgejo.org/2026-03-monthly-report/" rel="alternate"/>
    <category term="Forgejo" label="Forgejo"/>
    <published>2026-04-12T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" medium="image"/>
      <media:thumbnail url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp"/>
    </media:group>
    <dc:creator>Forgejo</dc:creator>
    <link rel="enclosure" href="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/763d33a62de2807c</id>
    <title>GitLab Patch Release: 18.10.3, 18.9.5, 18.8.9</title>
    <updated>2026-04-08T00:00:00+00:00</updated>
    <content>On April 8, 2026, we released versions 18.10.3, 18.9.5, 18.8.9 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to
one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action. GitLab releases fixes for vulnerabilities in patch releases. There are two types of patch re</content>
    <link href="https://docs.gitlab.com/releases/patches/patch-release-gitlab-18-10-3-released/" rel="alternate"/>
    <category term="GitLab Patch Releases" label="GitLab Patch Releases"/>
    <published>2026-04-08T00:00:00+00:00</published>
    <dc:creator>GitLab Patch Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/127fc0901dc523ed</id>
    <title>GitLab Patch Release: 18.10.1, 18.9.3, 18.8.7</title>
    <updated>2026-03-25T00:00:00+00:00</updated>
    <content>On March 25, 2026, we released versions 18.10.1, 18.9.3, 18.8.7 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to
one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action. GitLab releases fixes for vulnerabilities in patch releases. There are two types of patch r</content>
    <link href="https://docs.gitlab.com/releases/patches/patch-release-gitlab-18-10-1-released/" rel="alternate"/>
    <category term="GitLab Patch Releases" label="GitLab Patch Releases"/>
    <published>2026-03-25T00:00:00+00:00</published>
    <dc:creator>GitLab Patch Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/a9940fe80551675c</id>
    <title>GitLab 18.10 release notes</title>
    <updated>2026-03-19T00:00:00+00:00</updated>
    <content>On March 19, 2026, GitLab 18.10 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor. This month’s Notable Contributor: Harshith Sudar Harshith is currently a Level 3 Contributor who has made impactful contributions improving community tooling and analytics, from triage automation and contributor recognition to GitLab Duo usage insights. Harshith’s contributions were first recognized by Lee Tickett , Fullstack</content>
    <link href="https://docs.gitlab.com/releases/18/gitlab-18-10-released/" rel="alternate"/>
    <category term="GitLab Releases" label="GitLab Releases"/>
    <published>2026-03-19T00:00:00+00:00</published>
    <dc:creator>GitLab Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/5635468b3d08c38d</id>
    <title>GitLab Patch Release: 18.9.2, 18.8.6, 18.7.6</title>
    <updated>2026-03-11T00:00:00+00:00</updated>
    <content>On March 11, 2026, we released versions 18.9.2, 18.8.6, 18.7.6 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to
one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action. GitLab releases fixes for vulnerabilities in patch releases. There are two types of patch re</content>
    <link href="https://docs.gitlab.com/releases/patches/patch-release-gitlab-18-9-2-released/" rel="alternate"/>
    <category term="GitLab Patch Releases" label="GitLab Patch Releases"/>
    <published>2026-03-11T00:00:00+00:00</published>
    <dc:creator>GitLab Patch Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/d8d5e9e3e804fce3</id>
    <title>Forgejo monthly report - February 2026</title>
    <updated>2026-03-10T00:00:00+00:00</updated>
    <content>Forgejo was present at FOSDEM. The Forgejo runner received multiple bug fixes and new features. The helm chart received two minor changes. Improvements were made to the infrastructure.</content>
    <link href="https://forgejo.org/2026-02-monthly-report/" rel="alternate"/>
    <category term="Forgejo" label="Forgejo"/>
    <published>2026-03-10T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" medium="image"/>
      <media:thumbnail url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp"/>
    </media:group>
    <dc:creator>Forgejo</dc:creator>
    <link rel="enclosure" href="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/0cf2927d53881c92</id>
    <title>GitLab Patch Release: 18.9.1, 18.8.5, 18.7.5</title>
    <updated>2026-02-25T00:00:00+00:00</updated>
    <content>On February 25, 2026, we released versions 18.9.1, 18.8.5, 18.7.5 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to
one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action. GitLab releases fixes for vulnerabilities in patch releases. There are two types of patch</content>
    <link href="https://docs.gitlab.com/releases/patches/patch-release-gitlab-18-9-1-released/" rel="alternate"/>
    <category term="GitLab Patch Releases" label="GitLab Patch Releases"/>
    <published>2026-02-25T00:00:00+00:00</published>
    <dc:creator>GitLab Patch Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/77d2681e4f6e2347</id>
    <title>GitLab 18.9 release notes</title>
    <updated>2026-02-19T00:00:00+00:00</updated>
    <content>On February 19, 2026, GitLab 18.9 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor. This month’s Notable Contributor: Pooja Ghanghas Pooja has made significant contributions to ongoing efforts at GitLab to migrate legacy dropdown components to our modern dropdown architecture. These migrations require careful attention to detail and an understanding of both the old and new component systems. Pooja has cons</content>
    <link href="https://docs.gitlab.com/releases/18/gitlab-18-9-released/" rel="alternate"/>
    <category term="GitLab Releases" label="GitLab Releases"/>
    <published>2026-02-19T00:00:00+00:00</published>
    <dc:creator>GitLab Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/0402d529c45d34cc</id>
    <title>GitLab Patch Release: 18.8.4, 18.7.4, 18.6.6</title>
    <updated>2026-02-10T00:00:00+00:00</updated>
    <content>On February 10, 2026, we released versions 18.8.4, 18.7.4, 18.6.6 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to
one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action. GitLab releases fixes for vulnerabilities in patch releases. There are two types of patch</content>
    <link href="https://docs.gitlab.com/releases/patches/patch-release-gitlab-18-8-4-released/" rel="alternate"/>
    <category term="GitLab Patch Releases" label="GitLab Patch Releases"/>
    <published>2026-02-10T00:00:00+00:00</published>
    <dc:creator>GitLab Patch Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/89d14fc0889a0e6b</id>
    <title>GitLab AI Gateway Critical Patch Release: 18.6.2, 18.7.1, and 18.8.1</title>
    <updated>2026-02-06T00:00:00+00:00</updated>
    <content>On February 6, 2026, we released versions 18.6.2, 18.7.1, and 18.8.1 of the GitLab AI Gateway. These versions contain a critical security fix for GitLab Duo Self-Hosted AI Gateway, and we strongly recommend that all Self Managed customers with GitLab Duo Self-Hosted installations update to one of these versions immediately. A fix has already been deployed for the GitLab-hosted AI Gateway. Customers using GitLab.com, GitLab Dedicated, and GitLab Self Managed instances with GitLab-hosted AI Gatewa</content>
    <link href="https://docs.gitlab.com/releases/other-patches/patch-release-gitlab-ai-gateway-18-8-1-released/" rel="alternate"/>
    <category term="GitLab Patch Releases" label="GitLab Patch Releases"/>
    <published>2026-02-06T00:00:00+00:00</published>
    <dc:creator>GitLab Patch Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/cbf02ddd25a72828</id>
    <title>GitLab Patch Release: 18.8.3, 18.7.3, 18.6.5</title>
    <updated>2026-02-04T00:00:00+00:00</updated>
    <content>On February 4, 2026, we released versions 18.8.3, 18.7.3, and 18.6.5 for GitLab Community Edition and Enterprise Edition. This patch release delivers a set of targeted fixes focused on reliability, entitlement handling, and feature-flag consistency across GitLab Duo Agent Platform deployments. The updates reflect real-world usage across diverse environments and usage models, and are part of the normal hardening cycle for a platform that integrates deeply with GitLab workflows, identity, and usag</content>
    <link href="https://docs.gitlab.com/releases/patches/patch-release-gitlab-18-8-3-released/" rel="alternate"/>
    <category term="GitLab Patch Releases" label="GitLab Patch Releases"/>
    <published>2026-02-04T00:00:00+00:00</published>
    <dc:creator>GitLab Patch Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/011ae33e26595a43</id>
    <title>Forgejo monthly report - January 2026</title>
    <updated>2026-01-31T00:00:00+00:00</updated>
    <content>Forgejo v14 was released on time. Some regressions were quickly escalated and fixed. A security release was published for v11 and v13. A lot of work has been done around the runner – new features and QA. There are ongoing discussions about improving the issue reporting workflow and the license and copyright attribution in the codebase. Work on federation is progressing. The website was moved to our own infrastructure.</content>
    <link href="https://forgejo.org/2026-01-monthly-report/" rel="alternate"/>
    <category term="Forgejo" label="Forgejo"/>
    <published>2026-01-31T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" medium="image"/>
      <media:thumbnail url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp"/>
    </media:group>
    <dc:creator>Forgejo</dc:creator>
    <link rel="enclosure" href="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/5bc111160d8c106e</id>
    <title>GitLab Patch Release: 18.8.2, 18.7.2, 18.6.4</title>
    <updated>2026-01-21T00:00:00+00:00</updated>
    <content>On January 21, 2026, we released versions 18.8.2, 18.7.2, 18.6.4 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to
one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action. GitLab releases fixes for vulnerabilities in patch releases. There are two types of patch </content>
    <link href="https://docs.gitlab.com/releases/patches/patch-release-gitlab-18-8-2-released/" rel="alternate"/>
    <category term="GitLab Patch Releases" label="GitLab Patch Releases"/>
    <published>2026-01-21T00:00:00+00:00</published>
    <dc:creator>GitLab Patch Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/0b9c399c7f93dffa</id>
    <title>GitLab Patch Release: 18.8.1</title>
    <updated>2026-01-19T00:00:00+00:00</updated>
    <content>On January 19, 2026, we released versions 18.8.1 for GitLab Community Edition and Enterprise Edition. These versions resolve a number of regressions and bugs. This patch release does not include any security fixes. GitLab Community Edition and Enterprise Edition 18.8.1 Backport: Release AI Catalog External Agents Backport of ‘Fix summarize review prompt version for DAP Duo Code Review’ Backport of Disallow creation of new external agents Backport of Correct Code Review Flow history for beta Back</content>
    <link href="https://docs.gitlab.com/releases/patches/patch-release-gitlab-18-8-1-released/" rel="alternate"/>
    <category term="GitLab Patch Releases" label="GitLab Patch Releases"/>
    <published>2026-01-19T00:00:00+00:00</published>
    <dc:creator>GitLab Patch Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/ae6e5ed00d61385f</id>
    <title>Forgejo v14.0 is available</title>
    <updated>2026-01-15T00:00:00+00:00</updated>
    <content>Forgejo v14.0 is available. Issues search now has inline filters. Web file editor was replaced with CodeMirror. CSRF protection is now stateless. Forgejo actions gained new features and better trust management. Foreign keys are now supported to ensure database consistency.</content>
    <link href="https://forgejo.org/2026-01-release-v14-0/" rel="alternate"/>
    <category term="Forgejo" label="Forgejo"/>
    <published>2026-01-15T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" medium="image"/>
      <media:thumbnail url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp"/>
    </media:group>
    <dc:creator>Forgejo</dc:creator>
    <link rel="enclosure" href="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/fa6c70e8b42faa10</id>
    <title>GitLab 18.8 release notes</title>
    <updated>2026-01-15T00:00:00+00:00</updated>
    <content>On January 15, 2026, GitLab 18.8 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor. This month’s Notable Contributor: Wesley Yarde This month’s Notable Contributor is Wesley Yarde for building a foundational new feature that allows organizations to disable SSH keys for their enterprise users. Wesley’s contribution stands out for several reasons: Security and compliance : This feature enables organizations t</content>
    <link href="https://docs.gitlab.com/releases/18/gitlab-18-8-released/" rel="alternate"/>
    <category term="GitLab Releases" label="GitLab Releases"/>
    <published>2026-01-15T00:00:00+00:00</published>
    <dc:creator>GitLab Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/1060cb236cb08397</id>
    <title>GitLab Patch Release: 18.7.1, 18.6.3, 18.5.5</title>
    <updated>2026-01-07T00:00:00+00:00</updated>
    <content>On January 7, 2026, we released versions 18.7.1, 18.6.3, 18.5.5 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to
one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action. GitLab releases fixes for vulnerabilities in patch releases. There are two types of patch r</content>
    <link href="https://docs.gitlab.com/releases/patches/patch-release-gitlab-18-7-1-released/" rel="alternate"/>
    <category term="GitLab Patch Releases" label="GitLab Patch Releases"/>
    <published>2026-01-07T00:00:00+00:00</published>
    <dc:creator>GitLab Patch Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/7b302f1122c6c4e1</id>
    <title>GitLab 18.7 release notes</title>
    <updated>2025-12-18T00:00:00+00:00</updated>
    <content>On December 18, 2025, GitLab 18.7 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor. This month’s Notable Contributor: David Aniebo We’re excited to recognize David Aniebo as our 18.7 Notable Contributor for his impactful contributions to GitLab
product planning capabilities and the contributor platform . David’s work on improving work item list functionality demonstrates his technical expertise and dedicat</content>
    <link href="https://docs.gitlab.com/releases/18/gitlab-18-7-released/" rel="alternate"/>
    <category term="GitLab Releases" label="GitLab Releases"/>
    <published>2025-12-18T00:00:00+00:00</published>
    <dc:creator>GitLab Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/fca4ce0bd1f242c8</id>
    <title>GitLab Patch Release: 18.6.2, 18.5.4, 18.4.6</title>
    <updated>2025-12-10T00:00:00+00:00</updated>
    <content>On December 10, 2025, we released versions 18.6.2, 18.5.4, 18.4.6 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to
one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action. GitLab releases fixes for vulnerabilities in patch releases. There are two types of patch</content>
    <link href="https://docs.gitlab.com/releases/patches/patch-release-gitlab-18-6-2-released/" rel="alternate"/>
    <category term="GitLab Patch Releases" label="GitLab Patch Releases"/>
    <published>2025-12-10T00:00:00+00:00</published>
    <dc:creator>GitLab Patch Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/9e81314555cd3af2</id>
    <title>Forgejo monthly report - November 2025</title>
    <updated>2025-12-02T00:00:00+00:00</updated>
    <content>A security release was published for Forgejo v13 and v11 LTS. There is another way to report accessibility issues that lowers the barrier. User research is still seeking your help. A lot of work has been done regarding federation, and the Dutch government has expressed interest in Forgejo.</content>
    <link href="https://forgejo.org/2025-11-monthly-report/" rel="alternate"/>
    <category term="Forgejo" label="Forgejo"/>
    <published>2025-12-02T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" medium="image"/>
      <media:thumbnail url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp"/>
    </media:group>
    <dc:creator>Forgejo</dc:creator>
    <link rel="enclosure" href="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/26189cd8646eb785</id>
    <title>GitLab Patch Release: 18.6.1, 18.5.3, 18.4.5</title>
    <updated>2025-11-26T00:00:00+00:00</updated>
    <content>On November 26, 2025, we released versions 18.6.1, 18.5.3, 18.4.5 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to
one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action. GitLab releases fixes for vulnerabilities in patch releases. There are two types of patch</content>
    <link href="https://docs.gitlab.com/releases/patches/patch-release-gitlab-18-6-1-released/" rel="alternate"/>
    <category term="GitLab Patch Releases" label="GitLab Patch Releases"/>
    <published>2025-11-26T00:00:00+00:00</published>
    <dc:creator>GitLab Patch Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/2b3a3c39be2f2b56</id>
    <title>Letter from Codeberg: Onwards and upwards!</title>
    <updated>2025-11-21T23:00:00+00:00</updated>
    <content>(This is a stripped-down version of the newsletter sent out to Codeberg e. V. members as an email. The version emailed to our members contains some additional details concerning the association's Annual Assembly. If you are interested in helping us shape Codeberg, consider contributing or participating in our non-profit association …</content>
    <link href="https://blog.codeberg.org/letter-from-codeberg-onwards-and-upwards.html" rel="alternate"/>
    <category term="Codeberg" label="Codeberg"/>
    <published>2025-11-21T23:00:00+00:00</published>
    <dc:creator>Codeberg</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/0ed3dfd4de90039e</id>
    <title>GitLab 18.6 release notes</title>
    <updated>2025-11-20T00:00:00+00:00</updated>
    <content>On November 20, 2025, GitLab 18.6 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor. This month’s Notable Contributor: Samaksh Agarwal Every developer using the GitLab Development Kit (GDK) benefits from Samaksh’s contribution to improve the readability of gdk status .
While this enhancement may appear simple on the surface, it demonstrates exceptional attention to
developer experience and understanding of </content>
    <link href="https://docs.gitlab.com/releases/18/gitlab-18-6-released/" rel="alternate"/>
    <category term="GitLab Releases" label="GitLab Releases"/>
    <published>2025-11-20T00:00:00+00:00</published>
    <dc:creator>GitLab Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/681554d2532bdd12</id>
    <title>GitLab Patch Release: 18.5.2, 18.4.4, 18.3.6</title>
    <updated>2025-11-12T00:00:00+00:00</updated>
    <content>On November 12, 2025, we released versions 18.5.2, 18.4.4, 18.3.6 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to
one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action. GitLab releases fixes for vulnerabilities in patch releases. There are two types of patch</content>
    <link href="https://docs.gitlab.com/releases/patches/patch-release-gitlab-18-5-2-released/" rel="alternate"/>
    <category term="GitLab Patch Releases" label="GitLab Patch Releases"/>
    <published>2025-11-12T00:00:00+00:00</published>
    <dc:creator>GitLab Patch Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/99f8bb9c68e9fbb0</id>
    <title>Forgejo monthly report - October 2025</title>
    <updated>2025-11-08T00:00:00+00:00</updated>
    <content>Forgejo is 3 years old and was made possible by over 1,930 people and and many other free projects. Forgejo v13 was released and security vulnerabilities were fixed. Forgejo-contrib incubated new projects.</content>
    <link href="https://forgejo.org/2025-10-monthly-report/" rel="alternate"/>
    <category term="Forgejo" label="Forgejo"/>
    <published>2025-11-08T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" medium="image"/>
      <media:thumbnail url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp"/>
    </media:group>
    <dc:creator>Forgejo</dc:creator>
    <link rel="enclosure" href="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/eeacba946dc6d998</id>
    <title>GitLab Patch Release: 18.5.1, 18.4.3, 18.3.5</title>
    <updated>2025-10-22T00:00:00+00:00</updated>
    <content>On October 22, 2025, we released versions 18.5.1, 18.4.3, 18.3.5 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to
one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action. GitLab releases fixes for vulnerabilities in patch releases. There are two types of patch </content>
    <link href="https://docs.gitlab.com/releases/patches/patch-release-gitlab-18-5-1-released/" rel="alternate"/>
    <category term="GitLab Patch Releases" label="GitLab Patch Releases"/>
    <published>2025-10-22T00:00:00+00:00</published>
    <dc:creator>GitLab Patch Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/7648386ff95c30ca</id>
    <title>Forgejo v13.0 is available</title>
    <updated>2025-10-16T00:00:00+00:00</updated>
    <content>Forgejo v13.0 is available. A new moderation tool is available to report inappropriate user behavior or content that should be looked at by instance administrators. Two factor authentication (TOTP, etc.) can be enforced on the entire instance for all users or instance administrators. Forgejo Actions usability was improved with static checking of workflow files and access to the logs of all run attempts.</content>
    <link href="https://forgejo.org/2025-10-release-v13-0/" rel="alternate"/>
    <category term="Forgejo" label="Forgejo"/>
    <published>2025-10-16T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" medium="image"/>
      <media:thumbnail url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp"/>
    </media:group>
    <dc:creator>Forgejo</dc:creator>
    <link rel="enclosure" href="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/a45189ba2e6d279d</id>
    <title>GitLab 18.5 release notes</title>
    <updated>2025-10-16T00:00:00+00:00</updated>
    <content>On October 16, 2025, GitLab 18.5 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor. This month’s Notable Contributor: Jose Gabriel Companioni Benitez In his blog post “How GitLab Can Boost Your Professional Career” ,
Jose shares: “For me, the main advantage that GitLab offers, from a professional development
point of view, is that it is open source.” He adds, “For GitLab, it’s important
that anyone can cont</content>
    <link href="https://docs.gitlab.com/releases/18/gitlab-18-5-released/" rel="alternate"/>
    <category term="GitLab Releases" label="GitLab Releases"/>
    <published>2025-10-16T00:00:00+00:00</published>
    <dc:creator>GitLab Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/7326dfe0b0ae9f50</id>
    <title>Forgejo monthly report - September 2025</title>
    <updated>2025-10-02T00:00:00+00:00</updated>
    <content>The Forgejo v13.0 branch has been cut and the release is scheduled for October 16. Please consider testing it out and sharing your feedback to help us improve it. Forgejo Runner v11 has been released and is now licensed under GPLv3+. Improvements were made to the documentation regarding the Runner setup. Work on improving and securing database interaction has begun. There is an ongoing strong enthusiasm for translating Forgejo.</content>
    <link href="https://forgejo.org/2025-09-monthly-report/" rel="alternate"/>
    <category term="Forgejo" label="Forgejo"/>
    <published>2025-10-02T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" medium="image"/>
      <media:thumbnail url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp"/>
    </media:group>
    <dc:creator>Forgejo</dc:creator>
    <link rel="enclosure" href="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/54d6e0ef4000751a</id>
    <title>GitLab 18.4 release notes</title>
    <updated>2025-09-18T00:00:00+00:00</updated>
    <content>On September 18, 2025, GitLab 18.4 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor. This month’s Notable Contributor: Patrick Rice Patrick Rice continues his exceptional dedication to GitLab’s open source community as contributor, maintainer,
and mentor.
A top 5 contributor over the past year, Patrick maintains the GitLab Terraform Provider and client-go projects,
handling feature additions, releases, iss</content>
    <link href="https://docs.gitlab.com/releases/18/gitlab-18-4-released/" rel="alternate"/>
    <category term="GitLab Releases" label="GitLab Releases"/>
    <published>2025-09-18T00:00:00+00:00</published>
    <dc:creator>GitLab Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/519b4711eff2ac69</id>
    <title>Forgejo monthly report - August 2025</title>
    <updated>2025-09-05T00:00:00+00:00</updated>
    <content>A Forgejo security release was published, fixing nine low severity vulnerabilities. The Forgejo contributors agreed on rules for the use of AI and the documentation is nearly complete. The runner is considered secure enough to be used in production.</content>
    <link href="https://forgejo.org/2025-08-monthly-report/" rel="alternate"/>
    <category term="Forgejo" label="Forgejo"/>
    <published>2025-09-05T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" medium="image"/>
      <media:thumbnail url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp"/>
    </media:group>
    <dc:creator>Forgejo</dc:creator>
    <link rel="enclosure" href="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/f1e75cfbee9d3a96</id>
    <title>GitLab 18.3 release notes</title>
    <updated>2025-08-21T00:00:00+00:00</updated>
    <content>On August 21, 2025, GitLab 18.3 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor. This month’s Notable Contributor: Ahmed Kashkoush For 18.3, we’re excited to recognize Ahmed Kashkoush as our
Notable Contributor! Ahmed has been a standout contributor to the GitLab Web IDE through his Google Summer of Code participation this summer.
He has consistently delivered essential Git operations, directly addressing</content>
    <link href="https://docs.gitlab.com/releases/18/gitlab-18-3-released/" rel="alternate"/>
    <category term="GitLab Releases" label="GitLab Releases"/>
    <published>2025-08-21T00:00:00+00:00</published>
    <dc:creator>GitLab Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/a698caae6767cc4f</id>
    <title>Forgejo monthly report - July 2025</title>
    <updated>2025-08-04T00:00:00+00:00</updated>
    <content>The Forgejo v12 release was on time. The runner saw significant progress and the release tooling was improved. Discussions emerged regarding AI contributions, contributor attributions in the documentation, and the future of communication. An NLnet grant ended, allowing time for a retrospective.</content>
    <link href="https://forgejo.org/2025-07-monthly-report/" rel="alternate"/>
    <category term="Forgejo" label="Forgejo"/>
    <published>2025-08-04T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" medium="image"/>
      <media:thumbnail url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp"/>
    </media:group>
    <dc:creator>Forgejo</dc:creator>
    <link rel="enclosure" href="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/140e92f7fb51d48a</id>
    <title>Forgejo v12.0 is available</title>
    <updated>2025-07-17T00:00:00+00:00</updated>
    <content>Forgejo v12.0 is available. The User eXperience (UX) and User Interface were improved for the user profile page, the review of pull requests one commit at a time and Forgejo Actions notifications when a job fails. Pull request conflict checking was made faster and more resource efficient. SSH can be used instead of OpenPGP for instance signing. A default robots.txt is included by default to help mitigate excessive crawling. It also comes with a number of other UX, performance and security improv</content>
    <link href="https://forgejo.org/2025-07-release-v12-0/" rel="alternate"/>
    <category term="Forgejo" label="Forgejo"/>
    <published>2025-07-17T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" medium="image"/>
      <media:thumbnail url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp"/>
    </media:group>
    <dc:creator>Forgejo</dc:creator>
    <link rel="enclosure" href="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/5eceabffbef0e4d0</id>
    <title>GitLab 18.2 release notes</title>
    <updated>2025-07-17T00:00:00+00:00</updated>
    <content>On July 17, 2025, GitLab 18.2 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor. This month’s Notable Contributor: Markus Siebert Markus Siebert , a Platform Engineer at DB Systel GmbH, is leading the community effort to bring native AWS Secrets Manager support to GitLab CI/CD, addressing a critical enterprise need for secure secret management in pipelines. With an impressive 172 documented activities in ju</content>
    <link href="https://docs.gitlab.com/releases/18/gitlab-18-2-released/" rel="alternate"/>
    <category term="GitLab Releases" label="GitLab Releases"/>
    <published>2025-07-17T00:00:00+00:00</published>
    <dc:creator>GitLab Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/83febbe372de51b0</id>
    <title>Forgejo monthly report - June 2025</title>
    <updated>2025-07-01T00:00:00+00:00</updated>
    <content>Forgejo v12.0 branch was cut on 25 June, for a planned release on 17 July. Forgejo v11.0.2 was released on 18 June, addressing several bugs. Forgejo Runner v6.4.0 introduced offline caching support. The minimum required Git version has been bumped and the search has been improved. There is strong enthusiasm for translating Forgejo. User following with ActivityPub has progressed and a new NLnet grant has been accepted.</content>
    <link href="https://forgejo.org/2025-06-monthly-report/" rel="alternate"/>
    <category term="Forgejo" label="Forgejo"/>
    <published>2025-07-01T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" medium="image"/>
      <media:thumbnail url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp"/>
    </media:group>
    <dc:creator>Forgejo</dc:creator>
    <link rel="enclosure" href="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/bde71617aff6f2dc</id>
    <title>GitLab 18.1 release notes</title>
    <updated>2025-06-19T00:00:00+00:00</updated>
    <content>On June 19, 2025, GitLab 18.1 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor. This month’s Notable Contributor: Chaitanya Sonwane Chaitanya Sonwane drives GitLab’s security capabilities through consistent authentication
improvements. With 13 merged contributions in 2025 , his work enhanced credential inventory filtering, service account management, and work items usability.
He previously delivered a key </content>
    <link href="https://docs.gitlab.com/releases/18/gitlab-18-1-released/" rel="alternate"/>
    <category term="GitLab Releases" label="GitLab Releases"/>
    <published>2025-06-19T00:00:00+00:00</published>
    <dc:creator>GitLab Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/13018f2f1b497b52</id>
    <title>Letter from Codeberg: We love our new infrastructure</title>
    <updated>2025-06-11T22:00:00+00:00</updated>
    <content>(This is a stripped-down version of the news letters sent out to members of Codeberg e.V., in particular the newsletter for Codeberg e.V. members contains more details about e.V.-internal affairs and the annual assembly. If you are a member, please check this part in your email …</content>
    <link href="https://blog.codeberg.org/letter-from-codeberg-we-love-our-new-infrastructure.html" rel="alternate"/>
    <category term="Codeberg" label="Codeberg"/>
    <published>2025-06-11T22:00:00+00:00</published>
    <dc:creator>Codeberg</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/7342207bbd4ae5a4</id>
    <title>Forgejo monthly report - May 2025</title>
    <updated>2025-06-01T00:00:00+00:00</updated>
    <content>Ongoing issues with the Matrix chat room were addressed by recreating the room. Users are encouraged to join the new room, as the old room is deprecated. Security updates have been released for versions v11 and v7. Progress continues on the moderation feature funded by NLnet. Work on federated user activity continues, including the ability to follow Forgejo users from GoToSocial.</content>
    <link href="https://forgejo.org/2025-05-monthly-update/" rel="alternate"/>
    <category term="Forgejo" label="Forgejo"/>
    <published>2025-06-01T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" medium="image"/>
      <media:thumbnail url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp"/>
    </media:group>
    <dc:creator>Forgejo</dc:creator>
    <link rel="enclosure" href="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/5eba4ff3eabb2508</id>
    <title>GitLab 18.0 release notes</title>
    <updated>2025-05-15T00:00:00+00:00</updated>
    <content>On May 15, 2025, GitLab 18.0 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor. This month’s Notable Contributor: Michael Hofer Michael Hofer champions GitLab’s open source mission as both a top contributor and community leader.
With over 50 contributions this year,
his work strengthened GitLab’s Geo features and Secrets Manager, based on OpenBao.
He topped the April Hackathon while supporting fellow contri</content>
    <link href="https://docs.gitlab.com/releases/18/gitlab-18-0-released/" rel="alternate"/>
    <category term="GitLab Releases" label="GitLab Releases"/>
    <published>2025-05-15T00:00:00+00:00</published>
    <dc:creator>GitLab Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/d0310911d8a81f9e</id>
    <title>New storage limits on Codeberg: What you need to know</title>
    <updated>2025-05-13T22:00:00+00:00</updated>
    <content>In October 2024, we announced introducing a storage quota in a blog post which also shares a little more background. The goal is to leave more resources for the free/libre software projects that we all love, while reducing our spendings on abusive content and fighting it. We are now …</content>
    <link href="https://blog.codeberg.org/new-storage-limits-on-codeberg-what-you-need-to-know.html" rel="alternate"/>
    <category term="Codeberg" label="Codeberg"/>
    <published>2025-05-13T22:00:00+00:00</published>
    <dc:creator>Codeberg</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/808e4b61448bcd74</id>
    <title>Forgejo monthly report - April 2025</title>
    <updated>2025-05-01T00:00:00+00:00</updated>
    <content>Forgejo is now featured on the official Git website. Forgejo v11.0 was released on 16 April following quick fixes for identified regressions. The Helm chart was updated to version 12 for compatibility. Federation work continues on HTTP signatures and following user activity. The infrastructure faced SSH connection failures and excessive crawling.</content>
    <link href="https://forgejo.org/2025-04-monthly-update/" rel="alternate"/>
    <category term="Forgejo" label="Forgejo"/>
    <published>2025-05-01T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" medium="image"/>
      <media:thumbnail url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp"/>
    </media:group>
    <dc:creator>Forgejo</dc:creator>
    <link rel="enclosure" href="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/03f03b23c885f686</id>
    <title>GitLab 17.11 release notes</title>
    <updated>2025-04-17T00:00:00+00:00</updated>
    <content>On April 17, 2025, GitLab 17.11 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor. This month’s Notable Contributor: Heidi Berry For 17.11, we’re delighted to recognize Heidi Berry as our Notable Contributor! Heidi has been a standout contributor to the GitLab Terraform Provider and client-go projects. Over the past several releases, she has consistently delivered highly requested features including the abi</content>
    <link href="https://docs.gitlab.com/releases/17/gitlab-17-11-released/" rel="alternate"/>
    <category term="GitLab Releases" label="GitLab Releases"/>
    <published>2025-04-17T00:00:00+00:00</published>
    <dc:creator>GitLab Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/9019a104d3203df4</id>
    <title>Forgejo v11.0 is available</title>
    <updated>2025-04-16T00:00:00+00:00</updated>
    <content>Forgejo v11.0 is available. It comes with a number of new features and improvements making user experience more convenient and productive. It features a new UI language, easy access token regeneration, better search options, and makes it possible to download entire folders in one click. As an LTS version, it will be supported until 15 July 2026.</content>
    <link href="https://forgejo.org/2025-04-release-v11-0/" rel="alternate"/>
    <category term="Forgejo" label="Forgejo"/>
    <published>2025-04-16T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" medium="image"/>
      <media:thumbnail url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp"/>
    </media:group>
    <dc:creator>Forgejo</dc:creator>
    <link rel="enclosure" href="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/9717cf147dd96e91</id>
    <title>Forgejo monthly report - March 2025</title>
    <updated>2025-04-02T00:00:00+00:00</updated>
    <content>Forgejo v11.0 is on track for release on 16 April 2025. New versions of v7.0 and v10.0 have been released. Improvements to the availability of Forgejo actions have been completed and the Forgejo runner has received new versions. The DDoS attack on code.forgejo.org has ceased and precautions have been taken for the future.</content>
    <link href="https://forgejo.org/2025-03-monthly-update/" rel="alternate"/>
    <category term="Forgejo" label="Forgejo"/>
    <published>2025-04-02T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" medium="image"/>
      <media:thumbnail url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp"/>
    </media:group>
    <dc:creator>Forgejo</dc:creator>
    <link rel="enclosure" href="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/c03a4fcfa34914d5</id>
    <title>GitLab 17.10 release notes</title>
    <updated>2025-03-20T00:00:00+00:00</updated>
    <content>On March 20, 2025, GitLab 17.10 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor. This month’s Notable Contributor: Alexey Butkeev Everyone can nominate GitLab’s community contributors !
Show your support for our active candidates or add a new nomination! 🙌 Alexey Butkeev is a valued community contributor whose contributions enhance our global reach and user experience. His impactful localization and trans</content>
    <link href="https://docs.gitlab.com/releases/17/gitlab-17-10-released/" rel="alternate"/>
    <category term="GitLab Releases" label="GitLab Releases"/>
    <published>2025-03-20T00:00:00+00:00</published>
    <dc:creator>GitLab Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/f74c9cf7ea6b23c1</id>
    <title>Forgejo monthly report - February 2025</title>
    <updated>2025-03-19T00:00:00+00:00</updated>
    <content>FOSDEM impressions were published and feedback is being collected regarding migrations to Forgejo and commercial usages of Forgejo. code.forgejo.org got hit by a DDoS that was successfully mitigated. A new localization component is now in use and work on federation continued.</content>
    <link href="https://forgejo.org/2025-02-monthly-update/" rel="alternate"/>
    <category term="Forgejo" label="Forgejo"/>
    <published>2025-03-19T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" medium="image"/>
      <media:thumbnail url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp"/>
    </media:group>
    <dc:creator>Forgejo</dc:creator>
    <link rel="enclosure" href="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/be011d938935728c</id>
    <title>GitLab 17.9 release notes</title>
    <updated>2025-02-20T00:00:00+00:00</updated>
    <content>On February 20, 2025, GitLab 17.9 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor. This month’s Notable Contributor We’re excited to recognize Salihu Dickson as our MVP for his outstanding contributions to developing Comments on Wiki pages , a highly-requested feature that gathered over 200 positive reactions from the community! His dedication spanned over six months, delivering an implementation of wiki </content>
    <link href="https://docs.gitlab.com/releases/17/gitlab-17-9-released/" rel="alternate"/>
    <category term="GitLab Releases" label="GitLab Releases"/>
    <published>2025-02-20T00:00:00+00:00</published>
    <dc:creator>GitLab Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/e457b085a0300bf4</id>
    <title>We stay strong against hate and hatred</title>
    <updated>2025-02-11T23:00:00+00:00</updated>
    <content>Codeberg is currently suffering from hate campaigns due to far-right forces, and so are our users. First and foremost, we apologize for everyone who has recently received a notification email from our system containing offending and potentially traumatizing content. We are working hard on containing the effects on our users …</content>
    <link href="https://blog.codeberg.org/we-stay-strong-against-hate-and-hatred.html" rel="alternate"/>
    <category term="Codeberg" label="Codeberg"/>
    <published>2025-02-11T23:00:00+00:00</published>
    <dc:creator>Codeberg</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/62994ff7c7b9ce7f</id>
    <title>Forgejo monthly report - January 2025</title>
    <updated>2025-02-11T00:00:00+00:00</updated>
    <content>New releases, improvements to the website and an update to the current state of federation in Forgejo. January was a productive month that ended in preparations to FOSDEM and allowed some team members to meet in real life for the first time.</content>
    <link href="https://forgejo.org/2025-01-monthly-update/" rel="alternate"/>
    <category term="Forgejo" label="Forgejo"/>
    <published>2025-02-11T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" medium="image"/>
      <media:thumbnail url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp"/>
    </media:group>
    <dc:creator>Forgejo</dc:creator>
    <link rel="enclosure" href="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/a0cdcf2098a42116</id>
    <title>Forgejo Security Releases v10.0.1 and v7.0.13</title>
    <updated>2025-02-08T00:00:00+00:00</updated>
    <content>The Forgejo v10.0.1 and v7.0.13 releases contain critical security fixes related to permissions enforcement of web endpoints.</content>
    <link href="https://forgejo.org/2025-02-release-v10-0-1/" rel="alternate"/>
    <category term="Forgejo" label="Forgejo"/>
    <published>2025-02-08T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" medium="image"/>
      <media:thumbnail url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp"/>
    </media:group>
    <dc:creator>Forgejo</dc:creator>
    <link rel="enclosure" href="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/6d525e273c1be571</id>
    <title>Letter from Codeberg: Looking into 2025</title>
    <updated>2025-01-29T23:00:00+00:00</updated>
    <content>(This is a stripped-down version of the news letters sent out to members of Codeberg e.V. – not member of the non-profit association yet? Consider joining it! ) Dear Codeberg e.V. members and supporters! It is a pleasure for us to provide service to you. You are an awesome community …</content>
    <link href="https://blog.codeberg.org/letter-from-codeberg-looking-into-2025.html" rel="alternate"/>
    <category term="Codeberg" label="Codeberg"/>
    <published>2025-01-29T23:00:00+00:00</published>
    <dc:creator>Codeberg</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/3d70f64b7758c1b3</id>
    <title>Forgejo v10.0 is available</title>
    <updated>2025-01-16T00:00:00+00:00</updated>
    <content>Forgejo v10.0 is available. TOTP secrets were made more secure. The UI was made more accessible and reworked to improve the UX. Searching users, repositories, releases and issues was improved. Low German (Plattdüütsch) translation was completed. This is the last version to allow a transparent upgrade from Gitea v1.22 or lower.</content>
    <link href="https://forgejo.org/2025-01-release-v10-0/" rel="alternate"/>
    <category term="Forgejo" label="Forgejo"/>
    <published>2025-01-16T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" medium="image"/>
      <media:thumbnail url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp"/>
    </media:group>
    <dc:creator>Forgejo</dc:creator>
    <link rel="enclosure" href="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/5cf31068b7c7c840</id>
    <title>GitLab 17.8 release notes</title>
    <updated>2025-01-16T00:00:00+00:00</updated>
    <content>On January 16, 2025, GitLab 17.8 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor. This month’s Notable Contributor Everyone can nominate GitLab’s community contributors !
Show your support for our active candidates or add a new nomination! 🙌 Through the Co-Create Program, Océane Legrand has been leading efforts to enhance the Conan package registry feature set, collaborating with Juan Pablo Gonzalez.
Thei</content>
    <link href="https://docs.gitlab.com/releases/17/gitlab-17-8-released/" rel="alternate"/>
    <category term="GitLab Releases" label="GitLab Releases"/>
    <published>2025-01-16T00:00:00+00:00</published>
    <dc:creator>GitLab Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/065e2b38b0fa4936</id>
    <title>Forgejo monthly report - December 2024</title>
    <updated>2025-01-05T00:00:00+00:00</updated>
    <content>All the best for the new year from Forgejo. We are in the preparations for the upcoming v10 release, have improved testing and automation. A a big thanks to everyone who makes Forgejo a success, including upstream projects and libraries Forgejo depends on.</content>
    <link href="https://forgejo.org/2024-12-monthly-update/" rel="alternate"/>
    <category term="Forgejo" label="Forgejo"/>
    <published>2025-01-05T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" medium="image"/>
      <media:thumbnail url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp"/>
    </media:group>
    <dc:creator>Forgejo</dc:creator>
    <link rel="enclosure" href="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/950e7a4a9adecb00</id>
    <title>New event triggers for flows and external agents</title>
    <updated>2024-12-27T00:00:00+00:00</updated>
    <content>AI</content>
    <link href="https://docs.gitlab.com/releases/19/gitlab-19-1-released/#new-event-triggers-for-flows-and-external-agents" rel="alternate"/>
    <category term="GitLab What's New" label="GitLab What's New"/>
    <published>2024-12-27T00:00:00+00:00</published>
    <dc:creator>GitLab What's New</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/2d4cc0a9edc1316a</id>
    <title>Integrate third-party scanner results with GitLab (GA)</title>
    <updated>2024-12-25T00:00:00+00:00</updated>
    <content>Secure</content>
    <link href="https://docs.gitlab.com/user/application_security/detect/sarif/" rel="alternate"/>
    <category term="GitLab What's New" label="GitLab What's New"/>
    <published>2024-12-25T00:00:00+00:00</published>
    <dc:creator>GitLab What's New</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/688fbb4670526ec2</id>
    <title>GitLab 17.7 release notes</title>
    <updated>2024-12-19T00:00:00+00:00</updated>
    <content>On December 19, 2024, GitLab 17.7 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor. This month’s Notable Contributor: Vedant Jain Everyone can nominate GitLab’s community contributors !
Show your support for our active candidates or add a new nomination! 🙌 Vedant has been an outstanding community contributor, known for his proactive approach to contributing, his commitment to delivering, and his collaborat</content>
    <link href="https://docs.gitlab.com/releases/17/gitlab-17-7-released/" rel="alternate"/>
    <category term="GitLab Releases" label="GitLab Releases"/>
    <published>2024-12-19T00:00:00+00:00</published>
    <dc:creator>GitLab Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/44970d4057700571</id>
    <title>Gitea 1.22 is the last version to allow a transparent upgrade to Forgejo</title>
    <updated>2024-12-18T00:00:00+00:00</updated>
    <content>The Forgejo v10.0.0 release to be published 15 January 2025 supports upgrade from Gitea instances up to version v1.22 included. Future Forgejo versions will not support upgrades from Gitea instances running version v1.23 or above.</content>
    <link href="https://forgejo.org/2024-12-gitea-compatibility/" rel="alternate"/>
    <category term="Forgejo" label="Forgejo"/>
    <published>2024-12-18T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" medium="image"/>
      <media:thumbnail url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp"/>
    </media:group>
    <dc:creator>Forgejo</dc:creator>
    <link rel="enclosure" href="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/4a16f1112fca3c82</id>
    <title>Forgejo monthly report - November 2024</title>
    <updated>2024-12-05T00:00:00+00:00</updated>
    <content>A security audit and internal preparations have lead to unprecedented security releases for Forgejo and the Forgejo Actions runner. The migration to a new k8s cluster has made huge progress and is now powering the Forgejo-specific services in production. Improvements have been made to the performance and stability of Forgejo as well as to the automated testing process.</content>
    <link href="https://forgejo.org/2024-11-monthly-update/" rel="alternate"/>
    <category term="Forgejo" label="Forgejo"/>
    <published>2024-12-05T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" medium="image"/>
      <media:thumbnail url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp"/>
    </media:group>
    <dc:creator>Forgejo</dc:creator>
    <link rel="enclosure" href="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/187a2eca454d816b</id>
    <title>Improved secret detection coverage for feature branch pipelines (GA)</title>
    <updated>2024-11-25T00:00:00+00:00</updated>
    <content>Secure</content>
    <link href="https://docs.gitlab.com/user/application_security/secret_detection/pipeline/#coverage" rel="alternate"/>
    <category term="GitLab What's New" label="GitLab What's New"/>
    <published>2024-11-25T00:00:00+00:00</published>
    <dc:creator>GitLab What's New</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/0b8ac433ee7f8f88</id>
    <title>GitLab 17.6 release notes</title>
    <updated>2024-11-21T00:00:00+00:00</updated>
    <content>On November 21, 2024, GitLab 17.6 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor. This month’s Notable Contributor: Joel Gerber Everyone can nominate GitLab’s community contributors !
Show your support for our active candidates or add a new nomination! 🙌 Joel was recognized for being an invaluable contributor to our CI components, offering insightful feedback on merge requests,
and thoughtful comments on</content>
    <link href="https://docs.gitlab.com/releases/17/gitlab-17-6-released/" rel="alternate"/>
    <category term="GitLab Releases" label="GitLab Releases"/>
    <published>2024-11-21T00:00:00+00:00</published>
    <dc:creator>GitLab Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/c7778564d7d40c5a</id>
    <title>Why GitLab One platform for speed with control across your software lifecycle. Learn more</title>
    <updated>2024-11-15T00:00:00+00:00</updated>
    <content>One platform for speed with control across your software lifecycle.</content>
    <link href="https://about.gitlab.com/why-gitlab/" rel="alternate"/>
    <category term="GitLab Press" label="GitLab Press"/>
    <published>2024-11-15T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://about.gitlab.com/img/og?title=Why%20GitLab%3F" type="image/jpeg" medium="image"/>
      <media:thumbnail url="https://about.gitlab.com/img/og?title=Why%20GitLab%3F"/>
    </media:group>
    <dc:creator>GitLab Press</dc:creator>
    <link rel="enclosure" href="https://about.gitlab.com/img/og?title=Why%20GitLab%3F" type="image/jpeg" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/f61c8a8173d96335</id>
    <title>Forgejo monthly report - October 2024</title>
    <updated>2024-10-31T00:00:00+00:00</updated>
    <content>Forgejo is two years old and has been a lively human adventure, a story worth telling. A hackathon organized by Codeberg generated thousands of new translations. Forgejo v9.0.0 was published, as well as a security patch release which was backported to Forgejo v7, the six month old Long Term Support version. A kubernetes cluster was created to replace the current infrastructure, running Forgejo from the Helm Chart.</content>
    <link href="https://forgejo.org/2024-10-monthly-update/" rel="alternate"/>
    <category term="Forgejo" label="Forgejo"/>
    <published>2024-10-31T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" medium="image"/>
      <media:thumbnail url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp"/>
    </media:group>
    <dc:creator>Forgejo</dc:creator>
    <link rel="enclosure" href="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/cdcd5d879e2ffa62</id>
    <title>More power for you – what a storage quota will bring</title>
    <updated>2024-10-19T22:00:00+00:00</updated>
    <content>tl;dr? To make abuse prevention easier,
we are applying some default storage limits on Codeberg.
Free/libre software projects that need more will have to kindly request more resources . Dear Codeberg users,
the title sounds like a contradiction,
but that's exactly how we mean it. Ensuring a fair distribution …</content>
    <link href="https://blog.codeberg.org/more-power-for-you-what-a-storage-quota-will-bring.html" rel="alternate"/>
    <category term="Codeberg" label="Codeberg"/>
    <published>2024-10-19T22:00:00+00:00</published>
    <dc:creator>Codeberg</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/b6ab04d51474bc66</id>
    <title>GitLab 17.5 release notes</title>
    <updated>2024-10-17T00:00:00+00:00</updated>
    <content>On October 17, 2024, GitLab 17.5 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor. This month’s Notable Contributor: Jim Ender Everyone can nominate GitLab’s community contributors !
Show your support for our active candidates or add a new nomination! 🙌 Jim was recognized for leading an effort to close nearly 100 backlog issues on GitLab.
He is active in many of our weekly community pairing sessions that d</content>
    <link href="https://docs.gitlab.com/releases/17/gitlab-17-5-released/" rel="alternate"/>
    <category term="GitLab Releases" label="GitLab Releases"/>
    <published>2024-10-17T00:00:00+00:00</published>
    <dc:creator>GitLab Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/4147a45abcec679f</id>
    <title>Forgejo v9.0 is available</title>
    <updated>2024-10-16T00:00:00+00:00</updated>
    <content>Forgejo v9.0 is available. It is the first version to be released under a copyleft license. Forgejo has early support for a soft-quota that can protect your server from high disk usage due to abuse. It also removes support for go-git, considered too hazardous for daily usage compared to Git. The translations saw an unprecedented number of improvements thanks to the hackathon organized by Codeberg.</content>
    <link href="https://forgejo.org/2024-10-release-v9-0/" rel="alternate"/>
    <category term="Forgejo" label="Forgejo"/>
    <published>2024-10-16T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" medium="image"/>
      <media:thumbnail url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp"/>
    </media:group>
    <dc:creator>Forgejo</dc:creator>
    <link rel="enclosure" href="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/35fbbd819cb6ac34</id>
    <title>Generic secret detection (GA)</title>
    <updated>2024-10-15T00:00:00+00:00</updated>
    <content>Secure</content>
    <link href="https://docs.gitlab.com/user/application_security/secret_detection/" rel="alternate"/>
    <category term="GitLab What's New" label="GitLab What's New"/>
    <published>2024-10-15T00:00:00+00:00</published>
    <dc:creator>GitLab What's New</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/32833a9f9dddb864</id>
    <title>Forgejo monthly report - September 2024</title>
    <updated>2024-10-06T00:00:00+00:00</updated>
    <content>Forgejo v9.0 release candidates are available for testing to prepare for the release scheduled 16 October 2024. The contributor and testing documentation were improved with the goal of encouraging more diverse participation. The infrastructure dedicated to Forgejo development suffered a downtime because of excessive crawling and mitigation measures were implemented.</content>
    <link href="https://forgejo.org/2024-09-monthly-update/" rel="alternate"/>
    <category term="Forgejo" label="Forgejo"/>
    <published>2024-10-06T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" medium="image"/>
      <media:thumbnail url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp"/>
    </media:group>
    <dc:creator>Forgejo</dc:creator>
    <link rel="enclosure" href="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/d7ee5816f1f0636b</id>
    <title>Help us in making Forgejo v9 a great release</title>
    <updated>2024-09-25T00:00:00+00:00</updated>
    <content>Your help in preparing the next Forgejo release is appreciated. Now is a good time to step in.</content>
    <link href="https://forgejo.org/2024-09-preparing-v9/" rel="alternate"/>
    <category term="Forgejo" label="Forgejo"/>
    <published>2024-09-25T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" medium="image"/>
      <media:thumbnail url="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp"/>
    </media:group>
    <dc:creator>Forgejo</dc:creator>
    <link rel="enclosure" href="https://forgejo.org/_astro/og-preview.Uy75QWb0_6Lpd2.webp" type="image/webp" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/b9684b7f39ef9cfa</id>
    <title>GitLab 17.4 release notes</title>
    <updated>2024-09-19T00:00:00+00:00</updated>
    <content>On September 19, 2024, GitLab 17.4 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor. This month’s Notable Contributor: Archish Thakkar Everyone can nominate GitLab’s community contributors !
Show your support for our active candidates or add a new nomination! 🙌 Archish Thakkar is one of GitLab’s top contributors this year with 46 closed issues and 119 merged MRs . These contributions have helped Archish ea</content>
    <link href="https://docs.gitlab.com/releases/17/gitlab-17-4-released/" rel="alternate"/>
    <category term="GitLab Releases" label="GitLab Releases"/>
    <published>2024-09-19T00:00:00+00:00</published>
    <dc:creator>GitLab Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/fc66cfc7b93733c1</id>
    <title>Letter from Codeberg: Software is about humans</title>
    <updated>2024-09-02T22:00:00+00:00</updated>
    <content>(This is a stripped-down version of the news letters sent out to members of Codeberg e.V. – not member of the non-profit association yet? Consider joining it! ) Dear Codeberg e.V. Members and supporters! It's been a while since our last update. The past few months have been relatively calm …</content>
    <link href="https://blog.codeberg.org/letter-from-codeberg-software-is-about-humans.html" rel="alternate"/>
    <category term="Codeberg" label="Codeberg"/>
    <published>2024-09-02T22:00:00+00:00</published>
    <media:group>
      <media:content url="https://blog.codeberg.org/images/letter_2024_09_contract_signing.jpg" type="image/jpeg" medium="image"/>
      <media:thumbnail url="https://blog.codeberg.org/images/letter_2024_09_contract_signing.jpg"/>
    </media:group>
    <dc:creator>Codeberg</dc:creator>
    <link rel="enclosure" href="https://blog.codeberg.org/images/letter_2024_09_contract_signing.jpg" type="image/jpeg" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/7fa8ee01398f56f0</id>
    <title>GitLab 17.3 release notes</title>
    <updated>2024-08-15T00:00:00+00:00</updated>
    <content>On August 15, 2024, GitLab 17.3 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor. This month’s Notable Contributor: Anton Kalmykov Everyone can nominate GitLab’s community contributors !
Show your support for our active candidates or add a new nomination! 🙌 Anton Kalmykov is one of GitLab’s top contributors this year with 37 merged contributions since February and more in progress.
Anton is a Senior Fronte</content>
    <link href="https://docs.gitlab.com/releases/17/gitlab-17-3-released/" rel="alternate"/>
    <category term="GitLab Releases" label="GitLab Releases"/>
    <published>2024-08-15T00:00:00+00:00</published>
    <dc:creator>GitLab Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/d1087a9763af776a</id>
    <title>Secret false positive detection with GitLab Duo (GA)</title>
    <updated>2024-07-27T00:00:00+00:00</updated>
    <content>AI</content>
    <link href="https://docs.gitlab.com/user/application_security/vulnerabilities/secret_false_positive_detection/" rel="alternate"/>
    <category term="GitLab What's New" label="GitLab What's New"/>
    <published>2024-07-27T00:00:00+00:00</published>
    <dc:creator>GitLab What's New</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/4e6f816a72d75e38</id>
    <title>GitLab 17.2 release notes</title>
    <updated>2024-07-18T00:00:00+00:00</updated>
    <content>On July 18, 2024, GitLab 17.2 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor. This month’s Notable Contributor: Phawin Khongkhasawan Everyone can nominate GitLab’s community contributors !
Show your support for our active candidates or add a new nomination! 🙌 Phawin Khongkhasawan is a Tech Lead at Jitta and started contributing
to GitLab in February of 2024.
In just a few months, Phawin has merged over 2</content>
    <link href="https://docs.gitlab.com/releases/17/gitlab-17-2-released/" rel="alternate"/>
    <category term="GitLab Releases" label="GitLab Releases"/>
    <published>2024-07-18T00:00:00+00:00</published>
    <dc:creator>GitLab Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/006a67ba41cc6636</id>
    <title>GitLab 17.1 release notes</title>
    <updated>2024-06-20T00:00:00+00:00</updated>
    <content>On June 20, 2024, GitLab 17.1 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor. This month’s Notable Contributor Everyone can nominate GitLab’s community contributors !
Show your support for our active candidates or add a new nomination! 🙌 Shubham Kumar completed 7 issues during 17.1 and has been consistently contributing to GitLab since 2021.
He has now reached over 50 merged contributions!
Shubham is a G</content>
    <link href="https://docs.gitlab.com/releases/17/gitlab-17-1-released/" rel="alternate"/>
    <category term="GitLab Releases" label="GitLab Releases"/>
    <published>2024-06-20T00:00:00+00:00</published>
    <dc:creator>GitLab Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/cba3b04c07950794</id>
    <title>Stacked merge requests in the UI (GA)</title>
    <updated>2024-05-29T00:00:00+00:00</updated>
    <content>Code</content>
    <link href="https://docs.gitlab.com/user/project/merge_requests/reviews/stacked_merge_requests/" rel="alternate"/>
    <category term="GitLab What's New" label="GitLab What's New"/>
    <published>2024-05-29T00:00:00+00:00</published>
    <dc:creator>GitLab What's New</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/46562fb4aedfad20</id>
    <title>GitLab 17.0 release notes</title>
    <updated>2024-05-16T00:00:00+00:00</updated>
    <content>On May 16, 2024, GitLab 17.0 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor. This month’s Notable Contributor Everyone can nominate GitLab’s community contributors !
Show your support for our active candidates or add a new nomination 🙌 Niklas van Schrick now has the hat trick with three MVPs and has become one of GitLab’s most consistent contributors with at least one merge request per milestone since Gi</content>
    <link href="https://docs.gitlab.com/releases/17/gitlab-17-0-released/" rel="alternate"/>
    <category term="GitLab Releases" label="GitLab Releases"/>
    <published>2024-05-16T00:00:00+00:00</published>
    <dc:creator>GitLab Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/7994c65554cdd76e</id>
    <title>GitLab 16.11 release notes</title>
    <updated>2024-04-18T00:00:00+00:00</updated>
    <content>On April 18, 2024, GitLab 16.11 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor. This month’s Notable Contributor Ivan Shtyrliaiev has made half a dozen contributions to GitLab so far in 2024.
He was nominated by Hannah Sutor , Principal Product Manager at GitLab, who highlighted his contribution to improve the Users list search and filter experience . “This is a huge user experience improvement that help</content>
    <link href="https://docs.gitlab.com/releases/16/gitlab-16-11-released/" rel="alternate"/>
    <category term="GitLab Releases" label="GitLab Releases"/>
    <published>2024-04-18T00:00:00+00:00</published>
    <dc:creator>GitLab Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/65a0b814d186e014</id>
    <title>Security Review Flow (Beta)</title>
    <updated>2024-04-02T00:00:00+00:00</updated>
    <content>AI</content>
    <link href="https://docs.gitlab.com/user/duo_agent_platform/flows/foundational_flows/security_review/" rel="alternate"/>
    <category term="GitLab What's New" label="GitLab What's New"/>
    <published>2024-04-02T00:00:00+00:00</published>
    <dc:creator>GitLab What's New</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/2b86abdde73bfb02</id>
    <title>GitLab 16.10 release notes</title>
    <updated>2024-03-21T00:00:00+00:00</updated>
    <content>On March 21, 2024, GitLab 16.10 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor. This month’s Notable Contributor Lennard Sprong previously won the GitLab MVP award in 15.4 and
was also nominated in 16.9.
He continues to provide contributions to GitLab Workflow for VS Code, merging 8 contributions
in the past two months.
Some of his past contributions include the ability to watch the trace of running CI j</content>
    <link href="https://docs.gitlab.com/releases/16/gitlab-16-10-released/" rel="alternate"/>
    <category term="GitLab Releases" label="GitLab Releases"/>
    <published>2024-03-21T00:00:00+00:00</published>
    <dc:creator>GitLab Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/1e2c2f8768873415</id>
    <title>What we can learn from the Fediverse spam for Codeberg</title>
    <updated>2024-02-27T23:00:00+00:00</updated>
    <content>At Codeberg, we want to join the Fediverse,
the ActivityPub-powered world that connects Mastodon, Pixelfed, flohmarkt and so many other cool social networks and tools. Forgejo , the software that powers Codeberg,
is actively working on making this possible .
In our dreams, this will soon allow users on one server to …</content>
    <link href="https://blog.codeberg.org/what-we-can-learn-from-the-fediverse-spam-for-codeberg.html" rel="alternate"/>
    <category term="Codeberg" label="Codeberg"/>
    <published>2024-02-27T23:00:00+00:00</published>
    <dc:creator>Codeberg</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/bcb093baaf092d3f</id>
    <title>Git operation audit events for all actor types</title>
    <updated>2024-02-26T00:00:00+00:00</updated>
    <content>Secure</content>
    <link href="https://docs.gitlab.com/administration/compliance/audit_event_reports/" rel="alternate"/>
    <category term="GitLab What's New" label="GitLab What's New"/>
    <published>2024-02-26T00:00:00+00:00</published>
    <dc:creator>GitLab What's New</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/b01993b95bcf374c</id>
    <title>GitLab 16.9 release notes</title>
    <updated>2024-02-15T00:00:00+00:00</updated>
    <content>On February 15, 2024, GitLab 16.9 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor. This month’s Notable Contributor Ravi is actively working with GitLab’s Vulnerability Research group
to address high false-positive results in GitLab SAST. Ravi was nominated by Rohan Shah , Customer Success Manager at GitLab, who noted
Ravi’s significant improvements to the detection rules used in GitLab SAST. Dinesh Bolke</content>
    <link href="https://docs.gitlab.com/releases/16/gitlab-16-9-released/" rel="alternate"/>
    <category term="GitLab Releases" label="GitLab Releases"/>
    <published>2024-02-15T00:00:00+00:00</published>
    <dc:creator>GitLab Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/a0b0cb39ec31ffa5</id>
    <title>Tool approval guardrails for GitLab Duo agents</title>
    <updated>2024-02-12T00:00:00+00:00</updated>
    <content>AI</content>
    <link href="https://docs.gitlab.com/user/duo_agent_platform/agents/tool-governance/" rel="alternate"/>
    <category term="GitLab What's New" label="GitLab What's New"/>
    <published>2024-02-12T00:00:00+00:00</published>
    <dc:creator>GitLab What's New</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/1b1c5a6df613e797</id>
    <title>GPT models for Code Review Flow (GA)</title>
    <updated>2024-02-10T00:00:00+00:00</updated>
    <content>AI</content>
    <link href="https://docs.gitlab.com/user/duo_agent_platform/model_selection/#supported-models" rel="alternate"/>
    <category term="GitLab What's New" label="GitLab What's New"/>
    <published>2024-02-10T00:00:00+00:00</published>
    <dc:creator>GitLab What's New</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/7ed0014f4798dd49</id>
    <title>Security Manager role (GA)</title>
    <updated>2024-01-29T00:00:00+00:00</updated>
    <content>Secure</content>
    <link href="https://docs.gitlab.com/user/permissions/" rel="alternate"/>
    <category term="GitLab What's New" label="GitLab What's New"/>
    <published>2024-01-29T00:00:00+00:00</published>
    <dc:creator>GitLab What's New</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/fced0874f726d4d7</id>
    <title>Letter from Codeberg: Looking into the new year</title>
    <updated>2024-01-24T23:00:00+00:00</updated>
    <content>(This is a stripped-down version of the news letters sent out to members of Codeberg e.V. – not member of the non-profit association yet? Consider joining it! ) Dear Codeberg e.V. Members and supporters! We wish you all the best for 2024, including maximum success with your projects!
Let's have …</content>
    <link href="https://blog.codeberg.org/letter-from-codeberg-looking-into-the-new-year.html" rel="alternate"/>
    <category term="Codeberg" label="Codeberg"/>
    <published>2024-01-24T23:00:00+00:00</published>
    <dc:creator>Codeberg</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/8a267631ad10bf39</id>
    <title>GitLab 16.8 release notes</title>
    <updated>2024-01-18T00:00:00+00:00</updated>
    <content>On January 18, 2024, GitLab 16.8 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor. This month’s Notable Contributor Ted has made significant contributions removing old and unused code from our helper files and addressing other maintenance tasks.
He was nominated by Kerri Miller , Staff Engineer at GitLab, who said,
“It’s not always glamorous work, but it’s important work”. Ted is a freelance software engin</content>
    <link href="https://docs.gitlab.com/releases/16/gitlab-16-8-released/" rel="alternate"/>
    <category term="GitLab Releases" label="GitLab Releases"/>
    <published>2024-01-18T00:00:00+00:00</published>
    <dc:creator>GitLab Releases</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/edfd3d1c93c3532c</id>
    <title>What’s new in GitLab Stay updated with our latest features and improvements. Read the latest</title>
    <updated>2024-01-04T00:00:00+00:00</updated>
    <content>Stay updated with our latest features and improvements.</content>
    <link href="https://about.gitlab.com/whats-new/" rel="alternate"/>
    <category term="GitLab Press" label="GitLab Press"/>
    <published>2024-01-04T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://res.cloudinary.com/about-gitlab-com/image/upload/w_1200,h_630,c_fill,g_auto,f_png,q_auto/v1758207578/whxaklh4tf6nonryosrs.png" type="image/png" medium="image"/>
      <media:thumbnail url="https://res.cloudinary.com/about-gitlab-com/image/upload/w_1200,h_630,c_fill,g_auto,f_png,q_auto/v1758207578/whxaklh4tf6nonryosrs.png"/>
    </media:group>
    <dc:creator>GitLab Press</dc:creator>
    <link rel="enclosure" href="https://res.cloudinary.com/about-gitlab-com/image/upload/w_1200,h_630,c_fill,g_auto,f_png,q_auto/v1758207578/whxaklh4tf6nonryosrs.png" type="image/png" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/7d6fd5c7ba5690e4</id>
    <title>Model selection allowlist (Beta)</title>
    <updated>2023-12-21T00:00:00+00:00</updated>
    <content>AI</content>
    <link href="https://docs.gitlab.com/user/duo_agent_platform/model_selection/#select-a-model-for-agentic-chat" rel="alternate"/>
    <category term="GitLab What's New" label="GitLab What's New"/>
    <published>2023-12-21T00:00:00+00:00</published>
    <dc:creator>GitLab What's New</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/91bece43f30b59c0</id>
    <title>Scheduled pipeline execution policies (Beta)</title>
    <updated>2023-11-20T00:00:00+00:00</updated>
    <content>Secure</content>
    <link href="https://docs.gitlab.com/user/application_security/policies/scheduled_pipeline_execution_policies/" rel="alternate"/>
    <category term="GitLab What's New" label="GitLab What's New"/>
    <published>2023-11-20T00:00:00+00:00</published>
    <dc:creator>GitLab What's New</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/870e94ad1626045b</id>
    <title>One year into the war, your help is still needed</title>
    <updated>2023-11-09T23:00:00+00:00</updated>
    <content>(This text has been written a rather long time ago, with discussions starting in
Spring 2023. It took a while to draft, have Codeberg e. V. members vote and to finally
publish it. The latter was also due to other more important things in our
work queue. We apologize for …</content>
    <link href="https://blog.codeberg.org/one-year-into-the-war-your-help-is-still-needed.html" rel="alternate"/>
    <category term="Codeberg" label="Codeberg"/>
    <published>2023-11-09T23:00:00+00:00</published>
    <dc:creator>Codeberg</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/4303f264fa728447</id>
    <title>Letter from Codeberg: November 2023</title>
    <updated>2023-11-08T23:00:00+00:00</updated>
    <content>(This is a stripped-down version of the news letters sent out to members of Codeberg e.V. – not member of the non-profit association yet? Consider joining it! ) Dear Codeberg e.V. Members and supporters! Let's take some time to look at what we have achieved in the past months,
and …</content>
    <link href="https://blog.codeberg.org/letter-from-codeberg-november-2023.html" rel="alternate"/>
    <category term="Codeberg" label="Codeberg"/>
    <published>2023-11-08T23:00:00+00:00</published>
    <dc:creator>Codeberg</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/f502bdcd649c4161</id>
    <title>Disable built-in project templates</title>
    <updated>2023-10-10T00:00:00+00:00</updated>
    <content>Manage</content>
    <link href="https://docs.gitlab.com/administration/project_templates/#built-in-project-templates" rel="alternate"/>
    <category term="GitLab What's New" label="GitLab What's New"/>
    <published>2023-10-10T00:00:00+00:00</published>
    <dc:creator>GitLab What's New</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/286019b1262a3100</id>
    <title>Fine-grained Personal Access Tokens (GA)</title>
    <updated>2023-10-05T00:00:00+00:00</updated>
    <content>Secure</content>
    <link href="https://docs.gitlab.com/auth/tokens/fine_grained_access_tokens/" rel="alternate"/>
    <category term="GitLab What's New" label="GitLab What's New"/>
    <published>2023-10-05T00:00:00+00:00</published>
    <dc:creator>GitLab What's New</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/1af6b01c8f2b8508</id>
    <title>Stream AI audit events to external destinations (Beta)</title>
    <updated>2023-09-20T00:00:00+00:00</updated>
    <content>Secure</content>
    <link href="https://docs.gitlab.com/administration/compliance/audit_event_streaming/#ai-audit-event-streaming" rel="alternate"/>
    <category term="GitLab What's New" label="GitLab What's New"/>
    <published>2023-09-20T00:00:00+00:00</published>
    <dc:creator>GitLab What's New</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/3f6b971cb1a54bb8</id>
    <title>Letter from Codeberg: September 2023</title>
    <updated>2023-09-03T22:00:00+00:00</updated>
    <content>(This is a stripped-down version of the news letters sent out to members of Codeberg e.V. – not member of the non-profit association yet? Consider joining it! ) Dear Codeberg e.V. Members and supporters! Let's take some time to look at what we have achieved in the past months,
and …</content>
    <link href="https://blog.codeberg.org/letter-from-codeberg-september-2023.html" rel="alternate"/>
    <category term="Codeberg" label="Codeberg"/>
    <published>2023-09-03T22:00:00+00:00</published>
    <dc:creator>Codeberg</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/492f88c793b46c6f</id>
    <title>Custom and external AI feature controls (GA)</title>
    <updated>2023-09-03T00:00:00+00:00</updated>
    <content>AI</content>
    <link href="https://docs.gitlab.com/user/duo_agent_platform/" rel="alternate"/>
    <category term="GitLab What's New" label="GitLab What's New"/>
    <published>2023-09-03T00:00:00+00:00</published>
    <dc:creator>GitLab What's New</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/1486d480407a93ca</id>
    <title>The permissions for your scoped access tokens might change on Thursday</title>
    <updated>2023-08-06T22:00:00+00:00</updated>
    <content>Dear Codeberg users, we are excited to deploy Forgejo v1.20 to production, bringing tons of new features, bugfixes and improvements. However, there's a caveat with scoped access tokens: They will change, eventually granting more permissions than expected. Please read on if you use them. We additionally email all users …</content>
    <link href="https://blog.codeberg.org/the-permissions-for-your-scoped-access-tokens-might-change-on-thursday.html" rel="alternate"/>
    <category term="Codeberg" label="Codeberg"/>
    <published>2023-08-06T22:00:00+00:00</published>
    <dc:creator>Codeberg</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/de5eb7b7cbe497e4</id>
    <title>Support Assistant (Beta)</title>
    <updated>2023-07-26T00:00:00+00:00</updated>
    <content>AI</content>
    <link href="https://docs.gitlab.com/user/duo_agent_platform/agents/foundational_agents/support_assistant/" rel="alternate"/>
    <category term="GitLab What's New" label="GitLab What's New"/>
    <published>2023-07-26T00:00:00+00:00</published>
    <dc:creator>GitLab What's New</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/5170ba7b7b78ec95</id>
    <title>Custom flows YAML validation (GA)</title>
    <updated>2023-07-23T00:00:00+00:00</updated>
    <content>AI</content>
    <link href="https://docs.gitlab.com/user/duo_agent_platform/flows/custom/" rel="alternate"/>
    <category term="GitLab What's New" label="GitLab What's New"/>
    <published>2023-07-23T00:00:00+00:00</published>
    <dc:creator>GitLab What's New</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/692eaca9e2cfb46f</id>
    <title>Inline blame in the blob viewer (GA)</title>
    <updated>2023-07-09T00:00:00+00:00</updated>
    <content>Code</content>
    <link href="https://docs.gitlab.com/user/project/repository/files/git_blame/" rel="alternate"/>
    <category term="GitLab What's New" label="GitLab What's New"/>
    <published>2023-07-09T00:00:00+00:00</published>
    <dc:creator>GitLab What's New</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/bc2ae6db6c8d1b38</id>
    <title>Group-level custom instructions for Duo Code Review</title>
    <updated>2023-06-09T00:00:00+00:00</updated>
    <content>AI</content>
    <link href="https://docs.gitlab.com/user/project/merge_requests/duo_in_merge_requests/" rel="alternate"/>
    <category term="GitLab What's New" label="GitLab What's New"/>
    <published>2023-06-09T00:00:00+00:00</published>
    <dc:creator>GitLab What's New</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/a9f1ae5703c88327</id>
    <title>Fix CI/CD Pipeline Flow suggests targeted fixes</title>
    <updated>2023-06-06T00:00:00+00:00</updated>
    <content>AI</content>
    <link href="https://docs.gitlab.com/user/duo_agent_platform/flows/foundational_flows/fix_pipeline/" rel="alternate"/>
    <category term="GitLab What's New" label="GitLab What's New"/>
    <published>2023-06-06T00:00:00+00:00</published>
    <dc:creator>GitLab What's New</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/4e527d41bc0e9762</id>
    <title>Custom lifetime for OAuth access tokens (GA)</title>
    <updated>2023-05-26T00:00:00+00:00</updated>
    <content>Manage</content>
    <link href="https://docs.gitlab.com/administration/settings/account_and_limit_settings/#limit-the-lifetime-of-oauth-access-tokens" rel="alternate"/>
    <category term="GitLab What's New" label="GitLab What's New"/>
    <published>2023-05-26T00:00:00+00:00</published>
    <dc:creator>GitLab What's New</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/8de3736fb684760b</id>
    <title>Compliance framework templates (Beta)</title>
    <updated>2023-05-16T00:00:00+00:00</updated>
    <content>Secure</content>
    <link href="https://docs.gitlab.com/user/compliance/compliance_frameworks/#create-a-compliance-framework-from-a-template" rel="alternate"/>
    <category term="GitLab What's New" label="GitLab What's New"/>
    <published>2023-05-16T00:00:00+00:00</published>
    <dc:creator>GitLab What's New</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/1eb58484ee2ea9df</id>
    <title>Letter from Codeberg: May 2023</title>
    <updated>2023-05-14T22:00:00+00:00</updated>
    <content>(This is a stripped-down version of the news letters sent out to members of Codeberg e.V. – not member of the non-profit association yet? Consider joining it! ) Dear Codeberg e.V. Members and supporters! Our Annual Assembly for Codeberg e.V. legal members is nearing (May 21).
We now share …</content>
    <link href="https://blog.codeberg.org/letter-from-codeberg-may-2023.html" rel="alternate"/>
    <category term="Codeberg" label="Codeberg"/>
    <published>2023-05-14T22:00:00+00:00</published>
    <dc:creator>Codeberg</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/6722766587bd08c8</id>
    <title>Pattern-based tool approval for Agentic Chat (Beta)</title>
    <updated>2023-04-27T00:00:00+00:00</updated>
    <content>AI</content>
    <link href="https://docs.gitlab.com/user/gitlab_duo_chat/agentic_chat/#approve-tools-in-your-local-environment" rel="alternate"/>
    <category term="GitLab What's New" label="GitLab What's New"/>
    <published>2023-04-27T00:00:00+00:00</published>
    <dc:creator>GitLab What's New</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/8c77e10658e50553</id>
    <title>GitLab Security Standard Learn how to harden your software factory and let AI agents earn autonomy, without trading away security. Explore the standard</title>
    <updated>2023-04-14T00:00:00+00:00</updated>
    <content>Learn how to harden your software factory and let AI agents earn autonomy, without trading away security.</content>
    <link href="https://about.gitlab.com/gitlab-security-standard/" rel="alternate"/>
    <category term="GitLab Press" label="GitLab Press"/>
    <published>2023-04-14T00:00:00+00:00</published>
    <media:group>
      <media:content url="https://about.gitlab.com/img/og?title=The%20GitLab%20Security%20Standard%3A%20Securing%20your%20software%20factory" type="image/jpeg" medium="image"/>
      <media:thumbnail url="https://about.gitlab.com/img/og?title=The%20GitLab%20Security%20Standard%3A%20Securing%20your%20software%20factory"/>
    </media:group>
    <dc:creator>GitLab Press</dc:creator>
    <link rel="enclosure" href="https://about.gitlab.com/img/og?title=The%20GitLab%20Security%20Standard%3A%20Securing%20your%20software%20factory" type="image/jpeg" length="0"/>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/cd854d9c8d15cbc5</id>
    <title>Close coverage gaps with the Scanner Enablement Wizard (GA)</title>
    <updated>2023-04-07T00:00:00+00:00</updated>
    <content>Secure</content>
    <link href="https://docs.gitlab.com/user/application_security/configuration/scanner_enablement_wizard/" rel="alternate"/>
    <category term="GitLab What's New" label="GitLab What's New"/>
    <published>2023-04-07T00:00:00+00:00</published>
    <dc:creator>GitLab What's New</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/997d9ac80eeb9b62</id>
    <title>Automate assigning Code Owners as reviewers (GA)</title>
    <updated>2023-03-18T00:00:00+00:00</updated>
    <content>Code</content>
    <link href="https://docs.gitlab.com/user/project/merge_requests/reviews/automatic_reviewer_assignment/" rel="alternate"/>
    <category term="GitLab What's New" label="GitLab What's New"/>
    <published>2023-03-18T00:00:00+00:00</published>
    <dc:creator>GitLab What's New</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/ccbd19457a62f604</id>
    <title>Letter from Codeberg: Happy New Year!</title>
    <updated>2023-02-07T23:00:00+00:00</updated>
    <content>(This is a stripped-down version of the news letters sent out to members of Codeberg e.V. – not member of the non-profit association yet? Consider joining it! ) Dear Codeberg e.V. Members and supporters! The past months at Codeberg have been intense,
and it's overdue to share some updates. Organisational …</content>
    <link href="https://blog.codeberg.org/letter-from-codeberg-happy-new-year.html" rel="alternate"/>
    <category term="Codeberg" label="Codeberg"/>
    <published>2023-02-07T23:00:00+00:00</published>
    <dc:creator>Codeberg</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/0da1aa88da408bff</id>
    <title>The hardest scaling issue</title>
    <updated>2023-01-24T23:00:00+00:00</updated>
    <content>If you want to know more about our current technical scaling issues:
Rest assured that we are working hard on it.
Read on to learn why this is not as fast as you might expect. When people like me talk about scaling,
it is pretty obvious what we are referring …</content>
    <link href="https://blog.codeberg.org/the-hardest-scaling-issue.html" rel="alternate"/>
    <category term="Codeberg" label="Codeberg"/>
    <published>2023-01-24T23:00:00+00:00</published>
    <dc:creator>Codeberg</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/f62eff2ac12e4375</id>
    <title>GitLab Dependency Scanning Auto-Remediation (Beta)</title>
    <updated>2023-01-05T00:00:00+00:00</updated>
    <content>Secure</content>
    <link href="https://docs.gitlab.com/user/application_security/remediate/dependency_scanning_auto_remediation/" rel="alternate"/>
    <category term="GitLab What's New" label="GitLab What's New"/>
    <published>2023-01-05T00:00:00+00:00</published>
    <dc:creator>GitLab What's New</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/bd72c35ef8066e06</id>
    <title>How blocklists prevent the internet to be decentralized – and safe.</title>
    <updated>2022-12-25T23:00:00+00:00</updated>
    <content>TL;DR: We are currently experiencing recurring malware upload waves,
incurring pain to volunteers and disruptions for users we can do very little about.
Some thoughts to start a discussion. Safety on the Internet is crucial.
At Codeberg, we are working towards this goal every day.
Moderating a platform can …</content>
    <link href="https://blog.codeberg.org/how-blocklists-prevent-the-internet-to-be-decentralized-and-safe.html" rel="alternate"/>
    <category term="Codeberg" label="Codeberg"/>
    <published>2022-12-25T23:00:00+00:00</published>
    <dc:creator>Codeberg</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/adccffc7a733c4e1</id>
    <title>Codeberg launches Forgejo</title>
    <updated>2022-12-14T23:00:00+00:00</updated>
    <content>In October 2022, the Gitea Ltd for-profit company took over the Gitea project . Brodie Robertson clearly explains the trust issues created by a move that took the entire community by surprise, including the Codeberg presidium and members. This situation was worrisome, and sad. We should not fight our collaborators and …</content>
    <link href="https://blog.codeberg.org/codeberg-launches-forgejo.html" rel="alternate"/>
    <category term="Codeberg" label="Codeberg"/>
    <published>2022-12-14T23:00:00+00:00</published>
    <dc:creator>Codeberg</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/2a4fce843ddf123a</id>
    <title>Codeberg is moving ... and what this means to you</title>
    <updated>2022-11-12T23:00:00+00:00</updated>
    <content>Codeberg is moving, and you can imagine,
moving a mountain takes time and effort,
and might have a rocky road. TL;DR: Codeberg might suffer from decreased performance,
and smaller downtimes from Monday (Nov 14) to Wednesday (Nov 16).
Final migration will require a short period of planned downtime on …</content>
    <link href="https://blog.codeberg.org/codeberg-is-moving-and-what-this-means-to-you.html" rel="alternate"/>
    <category term="Codeberg" label="Codeberg"/>
    <published>2022-11-12T23:00:00+00:00</published>
    <dc:creator>Codeberg</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/1b250a091d62f5b2</id>
    <title>Letter from Codeberg: Hackathon, Translation Service &amp; more</title>
    <updated>2022-10-24T22:00:00+00:00</updated>
    <content>(This is a stripped-down version of the news letters sent out to members of Codeberg e.V. – not member of the non-profit association yet? Consider joining it! ) It's time for some updates,
we think there are some great news to share with you.
If you like what you read here …</content>
    <link href="https://blog.codeberg.org/letter-from-codeberg-hackathon-translation-service-more.html" rel="alternate"/>
    <category term="Codeberg" label="Codeberg"/>
    <published>2022-10-24T22:00:00+00:00</published>
    <dc:creator>Codeberg</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/c54317c1136c87c5</id>
    <title>Codeberg Hackathon goes v2</title>
    <updated>2022-10-21T22:00:00+00:00</updated>
    <content>TL;DR: We invite you to take part in the Codeberg Hackathon on the weekend starting Friday, 04th November 2022. We're doing it again:
A hackathon for Codeberg users, e.V.-members, interested developers, Free Software lovers and everyone else
who wants to lend us a helping hand. The goal …</content>
    <link href="https://blog.codeberg.org/codeberg-hackathon-goes-v2.html" rel="alternate"/>
    <category term="Codeberg" label="Codeberg"/>
    <published>2022-10-21T22:00:00+00:00</published>
    <dc:creator>Codeberg</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/6aaad967af0f3264</id>
    <title>Letter from Codeberg: New Landingpage and downtimes</title>
    <updated>2022-09-08T22:00:00+00:00</updated>
    <content>(This is a stripped-down version of the monthly news letters sent out to members of Codeberg e.V.; as usual published here with due delay. Not member of the non-profit association yet? Consider joining it! ) Dear Codeberg e.V. Members and Supporters! It's time for some updates.
We feel bad …</content>
    <link href="https://blog.codeberg.org/letter-from-codeberg-new-landingpage-and-downtimes.html" rel="alternate"/>
    <category term="Codeberg" label="Codeberg"/>
    <published>2022-09-08T22:00:00+00:00</published>
    <dc:creator>Codeberg</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/741d79349fc77ab8</id>
    <title>Letter from Codeberg: We are now an employer!</title>
    <updated>2022-06-14T22:00:00+00:00</updated>
    <content>(This is a stripped-down version of the monthly news letters sent out to members of Codeberg e.V.; as usual published here with due delay. Not member of the non-profit association yet? Consider joining it! ) Dear Codeberg e.V. Members and Supporters! It's been a while since the last monthly …</content>
    <link href="https://blog.codeberg.org/letter-from-codeberg-we-are-now-an-employer.html" rel="alternate"/>
    <category term="Codeberg" label="Codeberg"/>
    <published>2022-06-14T22:00:00+00:00</published>
    <dc:creator>Codeberg</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/621b813c8d59643e</id>
    <title>Monthly Report March and April 2022</title>
    <updated>2022-05-09T22:00:00+00:00</updated>
    <content>(This is a stripped-down version of the monthly news letters sent out to members of Codeberg e.V.; as usual published here with due delay. Not member of the non-profit association yet? Consider joining it! ) Dear Codeberg e.V. Members and Supporters! Let's share some news from March and April …</content>
    <link href="https://blog.codeberg.org/monthly-report-march-and-april-2022.html" rel="alternate"/>
    <category term="Codeberg" label="Codeberg"/>
    <published>2022-05-09T22:00:00+00:00</published>
    <dc:creator>Codeberg</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/d6799e174be4a951</id>
    <title>Let's bring Codeberg to the cloud</title>
    <updated>2022-03-31T22:00:00+00:00</updated>
    <content>In case you read this later and didn't yet spot the date: This was an April's Fool for 2022, please don't take it too serious. TL;DR: Our own hardware journey reaches the next level - we are finally moving fully to the cloud. About a year ago, we decided we'd …</content>
    <link href="https://blog.codeberg.org/lets-bring-codeberg-to-the-cloud.html" rel="alternate"/>
    <category term="Codeberg" label="Codeberg"/>
    <published>2022-03-31T22:00:00+00:00</published>
    <dc:creator>Codeberg</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/158b91b39c6ef841</id>
    <title>First Codeberg Hackathon in April 2022</title>
    <updated>2022-03-28T22:00:00+00:00</updated>
    <content>TL;DR: We invite you to take part in the Codeberg Hackathon on the weekend from April 8th to April 10th 2022 and help improving the ecosystem around Codeberg. We are taking collaborative notes in this HedgeDoc . Join the Senfcall (BigBlueButton meeting) (if no one is online, return at the …</content>
    <link href="https://blog.codeberg.org/first-codeberg-hackathon-in-april-2022.html" rel="alternate"/>
    <category term="Codeberg" label="Codeberg"/>
    <published>2022-03-28T22:00:00+00:00</published>
    <dc:creator>Codeberg</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/d92af97a37a4ec4a</id>
    <title>Introducing Gitea 1.16</title>
    <updated>2022-03-01T23:00:00+00:00</updated>
    <content>We finally deployed Gitea 1.16 a few days ago (on Friday, to be precise).
In case you missed it or didn't notice the changes,
I'll highlight what you need to know (not what you need to discover). We had to wait for the Gitea 1.16 release longer than …</content>
    <link href="https://blog.codeberg.org/introducing-gitea-116.html" rel="alternate"/>
    <category term="Codeberg" label="Codeberg"/>
    <published>2022-03-01T23:00:00+00:00</published>
    <dc:creator>Codeberg</dc:creator>
  </entry>
  <entry>
    <id>tag:trvny.github.io,2024:feedseek/gitlab/81f893e6322fbd42</id>
    <title>Monthly Report January 2022 - Hardware maintenance is hard!</title>
    <updated>2022-02-15T23:00:00+00:00</updated>
    <content>(This is a stripped-down version of the monthly news letter sent out to members of Codeberg e.V. this month; as usual published here with due delay. Not member of the non-profit association yet? Consider joining it! ) Dear Codeberg e.V. Members and Supporters! We are hosting 22020 repositories, created …</content>
    <link href="https://blog.codeberg.org/monthly-report-january-2022-hardware-maintenance-is-hard.html" rel="alternate"/>
    <category term="Codeberg" label="Codeberg"/>
    <published>2022-02-15T23:00:00+00:00</published>
    <dc:creator>Codeberg</dc:creator>
  </entry>
</feed>
