Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feed Updated 🍿 #87

Merged
merged 3 commits into from
Jun 2, 2024
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions config.json
Original file line number Diff line number Diff line change
@@ -1,11 +1,11 @@
{
"lastCheckTimestamp": 1716077354576,
"lastCheckTimestamp": 1717341976920,
"reposPaginationLimit": 250,
"releasePaginationLimit": 10,
"commentsPaginationLimit": 100,
"retrospective": {
"lastDay": "2024-02-11",
"nextDay": "2024-02-18"
"lastDay": "2024-02-18",
"nextDay": "2024-02-25"
},
"breakDelimiter": "</image>",
"discussionsInScope": [
Expand Down
107 changes: 106 additions & 1 deletion feed.xml
Original file line number Diff line number Diff line change
Expand Up @@ -8,12 +8,117 @@
<pubDate>Tue, 13 Jun 2023 04:17:50 GMT</pubDate>
<language>en-us</language>
<docs>https://validator.w3.org/feed/docs/rss2.html</docs>
<lastBuildDate>Sun, 19 May 2024 00:09:00 GMT</lastBuildDate>
<lastBuildDate>Sun, 02 Jun 2024 15:26:00 GMT</lastBuildDate>
<image>
<title>Node.js News</title>
<url>https://nodejs.org/static/images/logo-hexagon-card.png</url>
<link>https://github.com/nodejs/nodejs-news-feeder</link>
</image>
<item>
<title>Retrospective for nodejs from 2024-02-18 to 2024-02-25</title>
<description><![CDATA[<p>Reporting on 49 Issues from 25 authors, 51 Pull Requests from 27 authors, and 8 Discussions from 8 authors.</p>]]></description>
<pubDate>Sun, 18 Feb 2024 00:00:00 GMT</pubDate>
<link>https://github.com/cutenode/retro-weekly/blob/main/retros/2024-02-18.md</link>
<guid>https://github.com/cutenode/retro-weekly/blob/main/retros/2024-02-18.md</guid>
</item>
<item>
<title>Node.js Core update on 2024-05-27 04:17:32</title>
<description><![CDATA[<p>Is there a possibility of this being updated for 2024, IMO it feels outdated</p>
<p>(This being the pinned discussion)</p>
]]></description>
<pubDate>Mon, 27 May 2024 04:17:00 GMT</pubDate>
<link>https://github.com/orgs/nodejs/discussions/47703#discussioncomment-9565846</link>
<guid>https://github.com/orgs/nodejs/discussions/47703#discussioncomment-9565846</guid>
</item>
<item>
<title>Node.js Core update on 2024-05-27 20:09:26</title>
<description><![CDATA[<p>Given that there has been nothing shared ~for almost a full year~ ever, maybe we can unpin this, close it, and remove it from the documentation?</p>
]]></description>
<pubDate>Mon, 27 May 2024 20:09:00 GMT</pubDate>
<link>https://github.com/orgs/nodejs/discussions/47703#discussioncomment-9573565</link>
<guid>https://github.com/orgs/nodejs/discussions/47703#discussioncomment-9573565</guid>
</item>
<item>
<title>Node.js Core update on 2024-05-28 08:48:49</title>
<description><![CDATA[<p>Delivering news from the Node.js project POV seems to be a perennial issue. Folks like Michael have made efforts to improve this, but it doesn't fit into anyone's workflow enough to really stick. It reminds me of when you have a question at work, CC several people in, and no-one replies because they assume someone else was going to. :) (No judgment, BTW. This stuff is hard! And maybe there's a lot going on that I am unaware of.)</p>
<p>This may not be the place for such a discussion, but does/could the Node.js project have <em>one</em> individual on the inside to handle outreach/press/public representation? I've seen the ambassador program, which might well be intended to cover this(?), but I worry that spreading the role across multiple people could have a similar diluting effect.</p>
]]></description>
<pubDate>Tue, 28 May 2024 08:48:00 GMT</pubDate>
<link>https://github.com/orgs/nodejs/discussions/47703#discussioncomment-9578212</link>
<guid>https://github.com/orgs/nodejs/discussions/47703#discussioncomment-9578212</guid>
</item>
<item>
<title>Released nodejs/caritat v1.4.0</title>
<description><![CDATA[<p>Released nodejs/caritat v1.4.0 by github-actions[bot]. <a href="https://github.com/nodejs/caritat/releases/tag/v1.4.0">More details</a></p>
]]></description>
<pubDate>Sat, 01 Jun 2024 22:50:00 GMT</pubDate>
<link>https://github.com/nodejs/caritat/releases/tag/v1.4.0</link>
<guid>https://github.com/nodejs/caritat/releases/tag/v1.4.0</guid>
</item>
<item>
<title>Released nodejs/corepack v0.28.2</title>
<description><![CDATA[<p>Released nodejs/corepack v0.28.2 by github-actions[bot]. <a href="https://github.com/nodejs/corepack/releases/tag/v0.28.2">More details</a></p>
]]></description>
<pubDate>Fri, 31 May 2024 10:50:00 GMT</pubDate>
<link>https://github.com/nodejs/corepack/releases/tag/v0.28.2</link>
<guid>https://github.com/nodejs/corepack/releases/tag/v0.28.2</guid>
</item>
<item>
<title>Released nodejs/gyp-next v0.18.1</title>
<description><![CDATA[<p>Released nodejs/gyp-next v0.18.1 by github-actions[bot]. <a href="https://github.com/nodejs/gyp-next/releases/tag/v0.18.1">More details</a></p>
]]></description>
<pubDate>Wed, 29 May 2024 09:19:00 GMT</pubDate>
<link>https://github.com/nodejs/gyp-next/releases/tag/v0.18.1</link>
<guid>https://github.com/nodejs/gyp-next/releases/tag/v0.18.1</guid>
</item>
<item>
<title>Released nodejs/node v20.14.0</title>
<description><![CDATA[<p>Released nodejs/node v20.14.0 by marco-ippolito. <a href="https://github.com/nodejs/node/releases/tag/v20.14.0">More details</a></p>
]]></description>
<pubDate>Tue, 28 May 2024 16:55:00 GMT</pubDate>
<link>https://github.com/nodejs/node/releases/tag/v20.14.0</link>
<guid>https://github.com/nodejs/node/releases/tag/v20.14.0</guid>
</item>
<item>
<title>Released nodejs/node v18.20.3</title>
<description><![CDATA[<p>Released nodejs/node v18.20.3 by richardlau. <a href="https://github.com/nodejs/node/releases/tag/v18.20.3">More details</a></p>
]]></description>
<pubDate>Tue, 21 May 2024 12:18:00 GMT</pubDate>
<link>https://github.com/nodejs/node/releases/tag/v18.20.3</link>
<guid>https://github.com/nodejs/node/releases/tag/v18.20.3</guid>
</item>
<item>
<title>Released nodejs/node-core-utils v5.1.0</title>
<description><![CDATA[<p>Released nodejs/node-core-utils v5.1.0 by github-actions[bot]. <a href="https://github.com/nodejs/node-core-utils/releases/tag/v5.1.0">More details</a></p>
]]></description>
<pubDate>Wed, 22 May 2024 07:32:00 GMT</pubDate>
<link>https://github.com/nodejs/node-core-utils/releases/tag/v5.1.0</link>
<guid>https://github.com/nodejs/node-core-utils/releases/tag/v5.1.0</guid>
</item>
<item>
<title>Released nodejs/undici v6.18.2</title>
<description><![CDATA[<p>Released nodejs/undici v6.18.2 by github-actions[bot]. <a href="https://github.com/nodejs/undici/releases/tag/v6.18.2">More details</a></p>
]]></description>
<pubDate>Wed, 29 May 2024 13:33:00 GMT</pubDate>
<link>https://github.com/nodejs/undici/releases/tag/v6.18.2</link>
<guid>https://github.com/nodejs/undici/releases/tag/v6.18.2</guid>
</item>
<item>
<title>Released nodejs/undici v6.18.1</title>
<description><![CDATA[<p>Released nodejs/undici v6.18.1 by github-actions[bot]. <a href="https://github.com/nodejs/undici/releases/tag/v6.18.1">More details</a></p>
]]></description>
<pubDate>Wed, 22 May 2024 10:39:00 GMT</pubDate>
<link>https://github.com/nodejs/undici/releases/tag/v6.18.1</link>
<guid>https://github.com/nodejs/undici/releases/tag/v6.18.1</guid>
</item>
<item>
<title>Released nodejs/undici v6.18.0</title>
<description><![CDATA[<p>Released nodejs/undici v6.18.0 by github-actions[bot]. <a href="https://github.com/nodejs/undici/releases/tag/v6.18.0">More details</a></p>
]]></description>
<pubDate>Mon, 20 May 2024 13:00:00 GMT</pubDate>
<link>https://github.com/nodejs/undici/releases/tag/v6.18.0</link>
<guid>https://github.com/nodejs/undici/releases/tag/v6.18.0</guid>
</item>
<item>
<title>Retrospective for nodejs from 2024-02-11 to 2024-02-18</title>
<description><![CDATA[<p>Reporting on 40 Issues from 25 authors, 60 Pull Requests from 27 authors, and 10 Discussions from 10 authors.</p>]]></description>
Expand Down
209 changes: 209 additions & 0 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -176,6 +176,215 @@ <h2>Latest News</h2>
<div class="feed-items">


<hr>
<article>
<h3>
Retrospective for nodejs from 2024-02-18 to 2024-02-25
</h3>
<p>Reporting on 49 Issues from 25 authors, 51 Pull Requests from 27 authors, and 8 Discussions from 8 authors.</p>
<p class="feed-time">
Sun, 18 Feb 2024 00:00:00 GMT
</p>
<a class="feed-link" href="https://github.com/cutenode/retro-weekly/blob/main/retros/2024-02-18.md">
read more
</a>
</article>


<hr>
<article>
<h3>
Node.js Core update on 2024-05-27 04:17:32
</h3>
<p>Is there a possibility of this being updated for 2024, IMO it feels outdated</p>
<p>(This being the pinned discussion)</p>

<p class="feed-time">
Mon, 27 May 2024 04:17:00 GMT
</p>
<a class="feed-link" href="https://github.com/orgs/nodejs/discussions/47703#discussioncomment-9565846">
read more
</a>
</article>


<hr>
<article>
<h3>
Node.js Core update on 2024-05-27 20:09:26
</h3>
<p>Given that there has been nothing shared ~for almost a full year~ ever, maybe we can unpin this, close it, and remove it from the documentation?</p>

<p class="feed-time">
Mon, 27 May 2024 20:09:00 GMT
</p>
<a class="feed-link" href="https://github.com/orgs/nodejs/discussions/47703#discussioncomment-9573565">
read more
</a>
</article>


<hr>
<article>
<h3>
Node.js Core update on 2024-05-28 08:48:49
</h3>
<p>Delivering news from the Node.js project POV seems to be a perennial issue. Folks like Michael have made efforts to improve this, but it doesn't fit into anyone's workflow enough to really stick. It reminds me of when you have a question at work, CC several people in, and no-one replies because they assume someone else was going to. :) (No judgment, BTW. This stuff is hard! And maybe there's a lot going on that I am unaware of.)</p>
<p>This may not be the place for such a discussion, but does/could the Node.js project have <em>one</em> individual on the inside to handle outreach/press/public representation? I've seen the ambassador program, which might well be intended to cover this(?), but I worry that spreading the role across multiple people could have a similar diluting effect.</p>

<p class="feed-time">
Tue, 28 May 2024 08:48:00 GMT
</p>
<a class="feed-link" href="https://github.com/orgs/nodejs/discussions/47703#discussioncomment-9578212">
read more
</a>
</article>


<hr>
<article>
<h3>
Released nodejs/caritat v1.4.0
</h3>
<p>Released nodejs/caritat v1.4.0 by github-actions[bot]. <a href="https://github.com/nodejs/caritat/releases/tag/v1.4.0">More details</a></p>

<p class="feed-time">
Sat, 01 Jun 2024 22:50:00 GMT
</p>
<a class="feed-link" href="https://github.com/nodejs/caritat/releases/tag/v1.4.0">
read more
</a>
</article>


<hr>
<article>
<h3>
Released nodejs/corepack v0.28.2
</h3>
<p>Released nodejs/corepack v0.28.2 by github-actions[bot]. <a href="https://github.com/nodejs/corepack/releases/tag/v0.28.2">More details</a></p>

<p class="feed-time">
Fri, 31 May 2024 10:50:00 GMT
</p>
<a class="feed-link" href="https://github.com/nodejs/corepack/releases/tag/v0.28.2">
read more
</a>
</article>


<hr>
<article>
<h3>
Released nodejs/gyp-next v0.18.1
</h3>
<p>Released nodejs/gyp-next v0.18.1 by github-actions[bot]. <a href="https://github.com/nodejs/gyp-next/releases/tag/v0.18.1">More details</a></p>

<p class="feed-time">
Wed, 29 May 2024 09:19:00 GMT
</p>
<a class="feed-link" href="https://github.com/nodejs/gyp-next/releases/tag/v0.18.1">
read more
</a>
</article>


<hr>
<article>
<h3>
Released nodejs/node v20.14.0
</h3>
<p>Released nodejs/node v20.14.0 by marco-ippolito. <a href="https://github.com/nodejs/node/releases/tag/v20.14.0">More details</a></p>

<p class="feed-time">
Tue, 28 May 2024 16:55:00 GMT
</p>
<a class="feed-link" href="https://github.com/nodejs/node/releases/tag/v20.14.0">
read more
</a>
</article>


<hr>
<article>
<h3>
Released nodejs/node v18.20.3
</h3>
<p>Released nodejs/node v18.20.3 by richardlau. <a href="https://github.com/nodejs/node/releases/tag/v18.20.3">More details</a></p>

<p class="feed-time">
Tue, 21 May 2024 12:18:00 GMT
</p>
<a class="feed-link" href="https://github.com/nodejs/node/releases/tag/v18.20.3">
read more
</a>
</article>


<hr>
<article>
<h3>
Released nodejs/node-core-utils v5.1.0
</h3>
<p>Released nodejs/node-core-utils v5.1.0 by github-actions[bot]. <a href="https://github.com/nodejs/node-core-utils/releases/tag/v5.1.0">More details</a></p>

<p class="feed-time">
Wed, 22 May 2024 07:32:00 GMT
</p>
<a class="feed-link" href="https://github.com/nodejs/node-core-utils/releases/tag/v5.1.0">
read more
</a>
</article>


<hr>
<article>
<h3>
Released nodejs/undici v6.18.2
</h3>
<p>Released nodejs/undici v6.18.2 by github-actions[bot]. <a href="https://github.com/nodejs/undici/releases/tag/v6.18.2">More details</a></p>

<p class="feed-time">
Wed, 29 May 2024 13:33:00 GMT
</p>
<a class="feed-link" href="https://github.com/nodejs/undici/releases/tag/v6.18.2">
read more
</a>
</article>


<hr>
<article>
<h3>
Released nodejs/undici v6.18.1
</h3>
<p>Released nodejs/undici v6.18.1 by github-actions[bot]. <a href="https://github.com/nodejs/undici/releases/tag/v6.18.1">More details</a></p>

<p class="feed-time">
Wed, 22 May 2024 10:39:00 GMT
</p>
<a class="feed-link" href="https://github.com/nodejs/undici/releases/tag/v6.18.1">
read more
</a>
</article>


<hr>
<article>
<h3>
Released nodejs/undici v6.18.0
</h3>
<p>Released nodejs/undici v6.18.0 by github-actions[bot]. <a href="https://github.com/nodejs/undici/releases/tag/v6.18.0">More details</a></p>

<p class="feed-time">
Mon, 20 May 2024 13:00:00 GMT
</p>
<a class="feed-link" href="https://github.com/nodejs/undici/releases/tag/v6.18.0">
read more
</a>
</article>


<hr>
<article>
<h3>
Expand Down