<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>warnings on Abbreviatory.com</title>
    <link>https://abbreviatory.com/tags/warnings/</link>
    <description>Recent content in warnings on Abbreviatory.com</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 04 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://abbreviatory.com/tags/warnings/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Abbreviatory Now Tracks New Warnings and Runs as a GitHub Action</title>
      <link>https://abbreviatory.com/abbreviatory-now-tracks-new-warnings-and-runs-as-a-github-action/</link>
      <pubDate>Wed, 04 Nov 2026 00:00:00 +0000</pubDate>
      
      <guid>https://abbreviatory.com/abbreviatory-now-tracks-new-warnings-and-runs-as-a-github-action/</guid>
      <description>Warnings pile up. A build has forty of them, everyone stopped reading them months ago, and the one that matters, the deprecation that turns into an error next quarter, arrives as number forty-one. Abbreviatory has always kept warnings in its report. Until now it didn&amp;rsquo;t say which ones were new.
v0.6.0 does, behind a flag. Run with -warnings and a history, and the report compares warnings with the last run the way it already compares failures.</description>
    </item>
    
  </channel>
</rss>
