Azure DevOps Marketplace extension does not show latest devcontainers/ci release #444

Activity

1. deoli commented on Jul 29, 2026

   

   deoli

   on Jul 29, 2026

   More actions

   Todor Genov (@tgenov) It looks like the current version of the Azure DevOps extension might soon stop working. Please update the extension in the Marketplace. Thanks in advance!

   Task 'Devcontainers CI Task' version 0 (DevcontainersCi@0) is dependent on a Node version (16) that is end-of-life. Contact the extension owner for an updated version of the task. Task maintainers should review Node upgrade guidance: https://aka.ms/node-runner-guidance

   and

   Task relies on an unsupported version of Node.js. Unsupported Node versions (6, 10, and 16) are being retired, and any pipelines using tasks dependent on these versions will begin to fail. Learn More https://aka.ms/node-runner-guidance
2. michvllni commented on Oct 5, 2026

   

   Michael Villani (michvllni)

   on Oct 5, 2026

   Last edited by michvllni

   More actions

   Abdurrahmaan Iqbal (@abdurriq) would you be able to assist on this? The Azure DevOps task else will soon cease to work. It seems all that is needed is CI to push towards the Azure DevOps Marketplace.
3. tgenov commented on Oct 13, 2026

   

   Todor Genov (tgenov)

   on Oct 13, 2026

   Last edited by tgenov

   Contributor

   More actions

   Christof Marti (@chrmarti), a question about the Azure DevOps Marketplace publish.

   Current state

   • The Marketplace extension devcontainers.ci was last published on 2025-02-07 (0.3.1900000417). That version uses Node 16, which causes the warnings in this issue.
   • From 2025-10-16 to 2026-04-16, every CI (main) run failed in the "Run AzDO test" job with Dev container exec failed: (exit code: 255). Because of this failure, the "Create release" job did not run, so there was no publish.
   • The Node 20 change (Update Node, NPM, Go tools and Debian  #438, merged 2026-04-09) also failed in this job.
   • Add "Publish the AzDO extension" input #439, Also skip AzDO testing #440 and Fix conditions #441 (2026-04-16) disabled the AzDO steps. After this, the GitHub Action released again (run 24550939761). The AzDO extension stays unpublished.

   The logs of the failed runs are expired, so I cannot see the error. scripts/test-azdo.sh uses AZDO_TOKEN in its first command (tfx extension publish ... publisher devcontainers-dev). Thus an invalid token is possible, but I cannot confirm it.

   Question

   1. Do you know the error from "Run AzDO test" (for example, run 24520185906)?
   2. Is the AZDO_TOKEN secret still valid for the devcontainers and devcontainers-dev publishers, and does the AzDO test org/project still exist?

   Proposal

   When the cause is known, I can open a PR that:

   1. Enables the AzDO publish step again.
   2. Changes the DevcontainersMerge task (added in feat: native multi-platform builds via runner matrix (no QEMU emulation) #435) from Node16 to a supported handler. It now uses Node16 by mistake.
   3. Adds a Node24 handler to both tasks, with Node20 as fallback, because Node 20 is also end-of-life.

   I do not have access to the publisher or the secret. A maintainer must merge the PR and, if necessary, rotate the token. A maintainer must also decide if the publish step must stop the GitHub Action release when it fails.
4. tgenov commented on Oct 13, 2026

   

   Todor Genov (tgenov)

   on Oct 13, 2026

   Contributor

   More actions

   Fix: #448. It changes the task handlers to Node24 (with Node20_1 and Node16 as fallback) and enables the AzDO test and publish again. An AzDO failure does not block the GitHub Action release.

   Christof Marti (@chrmarti), /test cannot test the workflow change. Please see "Before merge" in #448: run "CI (branch)" to get a new AzDO log before the merge.