node-safe-resolve - Debian Package Tracker

action needed

version in VCS is newer than in repository, is it time to upload? normal

vcswatch reports that this package seems to have a new changelog entry (version 1.0.0-2, distribution UNRELEASED) and new commits in its VCS. You should consider whether it's time to make an upload.

Here are the relevant commit messages:

commit bbec48ae25a6b54ecd08a956456fcc8f671d2694
Author: Xavier Guimard <yadd@debian.org>
Date:   Tue May 12 22:28:01 2026 +0200

    debian/watch version 5

Created: 2026-05-12 Last update: 2026-05-12 22:33

testing migrations

excuses:
- Migration status for node-safe-resolve (- to 1.0.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- ∙ ∙ Autopkgtest for node-safe-resolve/1.0.0-1: amd64: Pass, arm64: Test triggered, i386: Test triggered, ppc64el: Test triggered, riscv64: Test triggered, s390x: Test triggered
- ∙ ∙ Too young, only 0 of 5 days old
- Additional info (not blocking):
- ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-safe-resolve.html
- ∙ ∙ Reproduced on amd64 - info
- ∙ ∙ Reproduced on arm64 - info
- ∙ ∙ Reproduced on armhf - info
- ∙ ∙ Reproduced on i386 - info
- Not considered

news

[2026-05-12] Accepted node-safe-resolve 1.0.0-1 (source all) into unstable (Debian FTP Masters) (signed by: Joe Nahmias)