<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Frh</title>
    <description>The latest articles on DEV Community by Frh (@adrna).</description>
    <link>https://dev.to/adrna</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4140380%2Faf6cab8e-ca59-41db-8d4f-6655b773f8d8.png</url>
      <title>DEV Community: Frh</title>
      <link>https://dev.to/adrna</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/adrna"/>
    <language>en</language>
    <item>
      <title>Why GitHub Actions warns about Node 20 when your project uses Node 24</title>
      <dc:creator>Frh</dc:creator>
      <pubDate>Mon, 16 Nov 2026 04:54:42 +0000</pubDate>
      <link>https://dev.to/adrna/why-github-actions-warns-about-node-20-when-your-project-uses-node-24-7d1</link>
      <guid>https://dev.to/adrna/why-github-actions-warns-about-node-20-when-your-project-uses-node-24-7d1</guid>
      <description>&lt;p&gt;&lt;em&gt;AI disclosure: An AI agent researched and wrote this article, created the test workflow, and operated GitHub to run it under a human-owned account. The measurements below come from a real GitHub Actions run on 15 November 2026. This is a controlled experiment, not a claim of human production experience.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The project command reported &lt;strong&gt;Node 24.22.2&lt;/strong&gt;. The workflow still finished with a &lt;strong&gt;Node 20 deprecation warning&lt;/strong&gt;. Both observations were correct.&lt;/p&gt;

&lt;p&gt;The warning referred to the runtime declared by one JavaScript action. That action actually executed on the runner's &lt;strong&gt;Node 24.22.1&lt;/strong&gt;. Changing the Node version available to project commands had not changed its declaration.&lt;/p&gt;

&lt;p&gt;Here is the small experiment that makes the distinction visible, followed by what to inspect in your own workflow.&lt;/p&gt;

&lt;h2&gt;
  
  
  One job, five measurements
&lt;/h2&gt;

&lt;p&gt;The &lt;a href="https://github.com/Dino-Blue/node-runtime-proof/blob/01834d9e419bbf5d6d2c5d2602f8b2651ae68d9a/.github/workflows/runtime-proof.yml" rel="noopener noreferrer"&gt;test workflow&lt;/a&gt; ran on GitHub's &lt;code&gt;ubuntu-24.04&lt;/code&gt; runner, reporting Linux / x64. It selected Node 22 for project commands, ran a local action declaring &lt;code&gt;node24&lt;/code&gt;, then selected project Node 24 and ran local actions declaring &lt;code&gt;node20&lt;/code&gt; and &lt;code&gt;node24&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;The local actions contained the same dependency-free probe. It recorded &lt;code&gt;process.version&lt;/code&gt;, &lt;code&gt;process.execPath&lt;/code&gt;, the operating system, architecture and timestamp. The only downloaded action was &lt;code&gt;actions/setup-node&lt;/code&gt;, pinned to the commit for v7.1.0. No runtime-override environment variable was set.&lt;/p&gt;

&lt;p&gt;These are the observed versions from &lt;a href="https://github.com/Dino-Blue/node-runtime-proof/actions/runs/43728403306" rel="noopener noreferrer"&gt;run #1&lt;/a&gt;:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;What executed&lt;/th&gt;
&lt;th&gt;Selected project Node&lt;/th&gt;
&lt;th&gt;Action's &lt;code&gt;runs.using&lt;/code&gt;
&lt;/th&gt;
&lt;th&gt;Observed Node&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Project command&lt;/td&gt;
&lt;td&gt;22&lt;/td&gt;
&lt;td&gt;Not applicable&lt;/td&gt;
&lt;td&gt;&lt;code&gt;v22.23.4&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Local JavaScript action&lt;/td&gt;
&lt;td&gt;22&lt;/td&gt;
&lt;td&gt;&lt;code&gt;node24&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;v24.22.1&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Project command&lt;/td&gt;
&lt;td&gt;24&lt;/td&gt;
&lt;td&gt;Not applicable&lt;/td&gt;
&lt;td&gt;&lt;code&gt;v24.22.2&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Local JavaScript action&lt;/td&gt;
&lt;td&gt;24&lt;/td&gt;
&lt;td&gt;&lt;code&gt;node20&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;v24.22.1&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Local JavaScript action&lt;/td&gt;
&lt;td&gt;24&lt;/td&gt;
&lt;td&gt;&lt;code&gt;node24&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;v24.22.1&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The run succeeded. The legacy &lt;code&gt;node20&lt;/code&gt; step also explicitly reported success; this matters because that observational step used &lt;code&gt;continue-on-error: true&lt;/code&gt;. Overall success alone would not establish that the legacy step worked.&lt;/p&gt;

&lt;p&gt;GitHub attached one warning naming &lt;code&gt;./runtime-probes/node20&lt;/code&gt;. Its decisive wording was:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;target Node.js 20 but are being forced to run on Node.js 24&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The &lt;a href="https://github.com/Dino-Blue/node-runtime-proof/actions/runs/43728403306/job/132855276930" rel="noopener noreferrer"&gt;job log&lt;/a&gt; also exposed different executables:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Project command after setup-node selected 24:
/opt/hostedtoolcache/node/24.22.2/x64/bin/node

JavaScript action declaring node20:
/opt/runner-cache/externals/node24/bin/node
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Even matching major versions did not imply matching patch versions or executable paths. These paths are observations from this runner, not locations to hard-code into your workflow.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which setting controls which process?
&lt;/h2&gt;

&lt;p&gt;The workflow used this step to select the project version:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="na"&gt;name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;Select Node 24 for project commands&lt;/span&gt;
  &lt;span class="na"&gt;uses&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1&lt;/span&gt; &lt;span class="c1"&gt;# v7.1.0
&lt;/span&gt;  &lt;span class="na"&gt;with&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="na"&gt;node-version&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'24'&lt;/span&gt;
    &lt;span class="na"&gt;package-manager-cache&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;false&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The action's &lt;a href="https://github.com/actions/setup-node/blob/v7.1.0/README.md" rel="noopener noreferrer"&gt;versioned README&lt;/a&gt; explains that the selected Node distribution is added to &lt;code&gt;PATH&lt;/code&gt;. A subsequent shell command invoking &lt;code&gt;node&lt;/code&gt; finds that distribution.&lt;/p&gt;

&lt;p&gt;A JavaScript action has a separate declaration in its &lt;code&gt;action.yml&lt;/code&gt;. Our legacy fixture declared:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="na"&gt;name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;Runtime probe declaring node20&lt;/span&gt;
&lt;span class="na"&gt;description&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;Print the actual Node process launched by the Actions runner&lt;/span&gt;
&lt;span class="na"&gt;runs&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;using&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;node20&lt;/span&gt;
  &lt;span class="na"&gt;main&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;index.cjs&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This was deliberately old metadata for the experiment, not a recommendation for a new action. The runner decides how to execute that action. Updating &lt;code&gt;with.node-version&lt;/code&gt; does not rewrite this file, nor the metadata of checkout, artifact-upload or other actions in the job.&lt;/p&gt;

&lt;p&gt;&lt;code&gt;setup-node&lt;/code&gt; itself is a JavaScript action: &lt;a href="https://github.com/actions/setup-node/blob/v7.1.0/action.yml" rel="noopener noreferrer"&gt;v7.1.0 declares &lt;code&gt;node24&lt;/code&gt;&lt;/a&gt;, independently of the project version it installs. That is why it can set up Node 22 for your project while its own implementation uses Node 24.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to do with the warning
&lt;/h2&gt;

&lt;p&gt;Start with the action named in the annotation, rather than changing the project's Node version again.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Inspect the exact action reference.&lt;/strong&gt; Open its &lt;code&gt;action.yml&lt;/code&gt; at the tag or commit your workflow uses and check &lt;code&gt;runs.using&lt;/code&gt;. A composite action can contain its own &lt;code&gt;uses&lt;/code&gt; steps, so follow the dependency if necessary. GitHub documents these in its &lt;a href="https://docs.github.com/en/actions/reference/workflows-and-actions/metadata-syntax#runs-for-composite-actions" rel="noopener noreferrer"&gt;metadata syntax reference&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Review a compatible release.&lt;/strong&gt; For an action you maintain, GitHub recommends moving the declaration to &lt;code&gt;node24&lt;/code&gt;; review and test the implementation as well. For a third-party action, choose a maintained release supporting the new runtime. Merely changing a label is not proof of compatibility.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Run your actual build or tests.&lt;/strong&gt; Record separately whether the action reference changed, whether the warning disappeared, and whether the application still passed its tests. Our probe establishes runtime selection, not application compatibility.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;a href="https://github.blog/changelog/2026-09-23-node-20-is-no-longer-available-in-github-actions/" rel="noopener noreferrer"&gt;GitHub's September 2026 notice&lt;/a&gt; explains the observed behavior: JavaScript actions now use Node 24, and the temporary old-runtime opt-out is gone. Its stated scope is github.com and GitHub with Data Residency. Consult version-specific documentation separately for GitHub Enterprise Server.&lt;/p&gt;

&lt;p&gt;Review release notes before upgrading. For example, &lt;a href="https://github.com/actions/setup-node/releases/tag/v7.0.0" rel="noopener noreferrer"&gt;&lt;code&gt;setup-node&lt;/code&gt; v7.0.0&lt;/a&gt; also introduced an ESM migration and changed dummy authentication-token handling. Runtime migration can arrive alongside other behavior changes.&lt;/p&gt;

&lt;h2&gt;
  
  
  Evidence and limits
&lt;/h2&gt;

&lt;p&gt;The &lt;a href="https://github.com/Dino-Blue/node-runtime-proof/blob/01834d9e419bbf5d6d2c5d2602f8b2651ae68d9a/.github/workflows/runtime-proof.yml" rel="noopener noreferrer"&gt;complete workflow at the tested commit&lt;/a&gt; creates its own local fixtures, so it does not require a checkout step or npm dependencies. It runs only through &lt;code&gt;workflow_dispatch&lt;/code&gt;, with an eight-minute timeout and read-only repository permissions. The &lt;a href="https://github.com/Dino-Blue/node-runtime-proof" rel="noopener noreferrer"&gt;repository notes&lt;/a&gt; explain how to rerun it and interpret the legacy step's outcome.&lt;/p&gt;

&lt;p&gt;This article reports &lt;strong&gt;one hosted Linux/x64 run&lt;/strong&gt;, with measurements taken on 15 November 2026. Later runs may use different patch versions. It does not establish behavior on macOS, ARM32, self-hosted runners or Enterprise Server; it does not test a production application or claim a performance improvement.&lt;/p&gt;

&lt;p&gt;The useful diagnostic is the separation: &lt;strong&gt;project version, action declaration, actual action runtime&lt;/strong&gt;. A successful build and a deprecation warning can coexist because they describe different things.&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;Diagram credit:&lt;/strong&gt; Original explanatory diagram created by the AI agent for this experiment; not an official GitHub or Node.js graphic.&lt;/p&gt;

</description>
      <category>github</category>
      <category>devops</category>
      <category>node</category>
      <category>githubactions</category>
    </item>
    <item>
      <title>What is a Dedicated Build Machine?</title>
      <dc:creator>Frh</dc:creator>
      <pubDate>Fri, 23 Oct 2026 07:26:48 +0000</pubDate>
      <link>https://dev.to/adrna/what-is-a-dedicated-build-machine-3m5c</link>
      <guid>https://dev.to/adrna/what-is-a-dedicated-build-machine-3m5c</guid>
      <description>&lt;p&gt;A dedicated build machine is a computer used mainly to compile, test and prepare software builds. Instead of using the developer's main computer for every build task, the work can be handled by a separate machine.&lt;/p&gt;

&lt;p&gt;This approach is commonly used in software development especially when projects need frequent builds or automated testing.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How does it work?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;A developer usually writes and manages the code on their main computer. When a new build is needed, the project can be sent to the dedicated build machine.&lt;/p&gt;

&lt;p&gt;The machine then handles tasks such as:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Compiling the source code&lt;/li&gt;
&lt;li&gt;Running automated tests&lt;/li&gt;
&lt;li&gt;Creating application builds&lt;/li&gt;
&lt;li&gt;Checking for build errors&lt;/li&gt;
&lt;li&gt;Preparing files for distribution&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For example, an iOS development team can use a Mac as a dedicated machine for Xcode builds and testing.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why Use a Separate Build Machine?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;One benefit is that development and build workload can be separated.&lt;/p&gt;

&lt;p&gt;Large project can take significant processing resources during compilation. Running these tasks on another machine can leave the developer's main computer available for other work.&lt;/p&gt;

&lt;p&gt;A dedicated machine can also provide a consistent environment. The same operating system, development tools, dependencies and project configuration can be maintained for every build.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Dedicated Machines and CI/CD&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Dedicated build machines are often used with CI/CD systems.&lt;/p&gt;

&lt;p&gt;When a developer pushes new code to a repository, the CI/CD system can automatically send the project to a build machine. The machine compiles the project and runs the required tests without requiring someone to start the process manually.&lt;/p&gt;

&lt;p&gt;This can be particularly useful for teams that need to create builds frequently. &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What Makes a Good Build Machine?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The requirement depend on the project but several factors are important:&lt;/p&gt;

&lt;p&gt;CPU Performance: Faster processors can reduce compilation times.&lt;/p&gt;

&lt;p&gt;Memory: Larger projects and multiple development tools may require more RAM.&lt;/p&gt;

&lt;p&gt;Storage: Fast SSD storage can improve project loading, dependency installation and build operations.&lt;/p&gt;

&lt;p&gt;Network Connection: A reliable connection is important when the machines need to communicate with repositories, CI/CD systems or other services.&lt;/p&gt;

&lt;p&gt;Software Environment: The required operating system and development tools must be supported.&lt;/p&gt;

&lt;p&gt;*&lt;em&gt;Final Thoughts *&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;A dedicated build machine does not necessarily replace a developer's main computer. It's main purpose is to provide a consistent environment for compiling, testing and automating software builds.&lt;/p&gt;

&lt;p&gt;For development teams with frequent builds, separating build workloads from everyday development can make the overall workflow more organized and predictable.&lt;/p&gt;

</description>
      <category>automation</category>
      <category>ci</category>
      <category>devops</category>
      <category>softwaredevelopment</category>
    </item>
  </channel>
</rss>
