<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Json on rmqa.com</title>
    <link>https://rmqa.com/tags/json/</link>
    <description>Recent content in Json on rmqa.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 25 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://rmqa.com/tags/json/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Keeping a Machine-Readable Record of What Every Release Shipped</title>
      <link>https://rmqa.com/keeping-a-machine-readable-record-of-what-every-release-shipped/</link>
      <pubDate>Sun, 25 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://rmqa.com/keeping-a-machine-readable-record-of-what-every-release-shipped/</guid>
      <description>&lt;p&gt;Sooner or later someone asks what exactly was in a release. A customer whose security team wants to know which build of a program they&amp;rsquo;re running. An auditor working through a supply-chain questionnaire. A colleague trying to work out, a year later, whether the Windows download of version 2.3.0 had the fix in it.&lt;/p&gt;&#xA;&lt;p&gt;The release page answers part of that: file names and sizes. It doesn&amp;rsquo;t say what was inside the archives, which platform each program was built for, or whether anyone checked. rmqa&amp;rsquo;s JSON report does, and it costs nothing to keep.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
