published date format is not conforming to RFC3339 #3582
Description
In this example
<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
<id>tag:libraries.io,2005:/npm/@azure-tools/openai-typespec/versions</id>
<link rel="alternate" type="text/html" href="https://libraries.io"/>
<link rel="self" type="application/atom+xml" href="https://libraries.io/npm/@azure-tools/openai-typespec/versions.atom"/>
<title>@azure-tools/openai-typespec versions - Libraries.io</title>
<updated>2026-01-06T20:26:23Z</updated>
<entry>
<id>tag:libraries.io,2005:Version/134857947</id>
<published>2026-01-06T20:30:02Z</published>
<updated>2026-01-06T20:30:02Z</updated>
<link rel="alternate" type="text/html" href="https://libraries.io/npm/@azure-tools%2Fopenai-typespec/0.1.9"/>
<title>0.1.9</title>
<published>Tue, 06 Jan 2026 20:26:23 +0000</published>
<content type="html"></content>
<author>
<name>Libraries.io</name>
</author>
</entry>
<entry>
<id>tag:libraries.io,2005:Version/134169107</id>
<published>2025-12-26T21:15:06Z</published>
<updated>2025-12-26T21:15:06Z</updated>
<link rel="alternate" type="text/html" href="https://libraries.io/npm/@azure-tools%2Fopenai-typespec/0.1.8"/>
<title>0.1.8</title>
<published>Fri, 26 Dec 2025 21:11:13 +0000</published>
<content type="html"></content>
<author>
<name>Libraries.io</name>
</author>
</entry>
<entry>
<id>tag:libraries.io,2005:Version/133942528</id>
<published>2025-12-23T00:00:16Z</published>
<updated>2025-12-23T00:00:16Z</updated>
<link rel="alternate" type="text/html" href="https://libraries.io/npm/@azure-tools%2Fopenai-typespec/0.1.7"/>
<title>0.1.7</title>
<published>Mon, 22 Dec 2025 23:59:20 +0000</published>
<content type="html"></content>
<author>
<name>Libraries.io</name>
</author>
</entry>
<entry>
<id>tag:libraries.io,2005:Version/133930023</id>
<published>2025-12-22T19:45:06Z</published>
<updated>2025-12-22T19:45:06Z</updated>
<link rel="alternate" type="text/html" href="https://libraries.io/npm/@azure-tools%2Fopenai-typespec/0.1.6"/>
<title>0.1.6</title>
<published>Mon, 22 Dec 2025 19:42:12 +0000</published>
<content type="html"></content>
<author>
<name>Libraries.io</name>
</author>
</entry>
<entry>
<id>tag:libraries.io,2005:Version/133503870</id>
<published>2025-12-17T03:05:01Z</published>
<updated>2025-12-17T03:05:01Z</updated>
<link rel="alternate" type="text/html" href="https://libraries.io/npm/@azure-tools%2Fopenai-typespec/0.1.5"/>
<title>0.1.5</title>
<published>Wed, 17 Dec 2025 03:01:18 +0000</published>
<content type="html"></content>
<author>
<name>Libraries.io</name>
</author>
</entry>
<entry>
<id>tag:libraries.io,2005:Version/133503865</id>
<published>2025-12-17T03:05:01Z</published>
<updated>2025-12-17T03:05:01Z</updated>
<link rel="alternate" type="text/html" href="https://libraries.io/npm/@azure-tools%2Fopenai-typespec/0.1.4"/>
<title>0.1.4</title>
<published>Fri, 12 Dec 2025 20:07:01 +0000</published>
<content type="html"></content>
<author>
<name>Libraries.io</name>
</author>
</entry>
<entry>
<id>tag:libraries.io,2005:Version/133183851</id>
<published>2025-12-12T20:00:08Z</published>
<updated>2025-12-12T20:00:08Z</updated>
<link rel="alternate" type="text/html" href="https://libraries.io/npm/@azure-tools%2Fopenai-typespec/0.1.3"/>
<title>0.1.3</title>
<published>Fri, 12 Dec 2025 19:59:45 +0000</published>
<content type="html"></content>
<author>
<name>Libraries.io</name>
</author>
</entry>
<entry>
<id>tag:libraries.io,2005:Version/130911353</id>
<published>2025-11-12T18:25:29Z</published>
<updated>2025-11-12T18:25:29Z</updated>
<link rel="alternate" type="text/html" href="https://libraries.io/npm/@azure-tools%2Fopenai-typespec/0.1.1"/>
<title>0.1.1</title>
<published>Wed, 12 Nov 2025 18:24:06 +0000</published>
<content type="html"></content>
<author>
<name>Libraries.io</name>
</author>
</entry>
</feed>The published date field contains Tue, 06 Jan 2026 20:26:23 +0000 which is not valid according to the RFC 4287, it should follow the RFC 3339 format, it should instead be 2026-01-06T20:26:23Z
This causes atom parsers to fail. Interestingly, the field is present twice for some reason, and should only be present once according to the specification, the first published field contains a slightly different value, but it's formatted properly and is close enough to be useful for consumption.
I suggest the serialization should be fixed to provide AT MOST a single value and for that value to be formatted correctly.