Watch file results
component: main
debian_mangled_uversion: 22.21.1+~cs22.19.0
debian_uversion: 22.21.1+dfsg+~cs22.19.1
distribution: debian
last_check: 2025-11-27 05:20:16.332986
metadata: --- Archive: GitHub Bug-Database: https://github.com/nodejs/node/issues Bug-Submit: https://github.com/nodejs/node/issues/new Changelog: https://github.com/nodejs/node/tags Repository: https://github.com/nodejs/node.git Repository-Browse: https://github.com/nodejs/node Security-Contact: https://github.com/nodejs/node/tree/HEAD/SECURITY.md
release: sid
source: nodejs
status: newer package available
upstream_url: https://nodejs.org/dist/v22.21.1/node-v22.21.1.tar.xz
upstream_version: 22.21.1+~cs22.19.1
version: 22.21.1+dfsg+~cs22.19.0-5
watch_file:
Version: 5 Source: https://nodejs.org/dist Matching-Pattern: v(22\.\d+\.\d+)/ Downloadurlmangle: s/.*v(.*)\//https\:\/\/nodejs\.org\/dist\/v$1\/node\-v$1\.tar\.xz/ Dversionmangle: auto Filenamemangle: s/.*v(.*)\/$/nodejs-$1\.tar\.xz/ Repacksuffix: +dfsg Version-Schema: group # IMPORTANT: do NOT upgrade @types/node when target is debian/stable, # it will break some debian packages, and some users packages too. # It is not recommended use npmregistry. Please investigate more. # Take a look at https://wiki.debian.org/debian/watch/ Component: types-node Template: Npmregistry Ctype: nodejs Dist: @types/node Matching-Pattern: https://registry.npmjs.org/@types/node/-/node-(22\.\d+\.\d+)@ARCHIVE_EXT@ Version-Schema: checksum