Is passthru.updateScript = nix-update-script {}; redundant?

I was adding it to obs-cmd some time ago to bump it to 1.0.0, but now I noticed the package updated without it:

$ git log -1 -- pkgs/by-name/ob/obs-cmd/package.nix
commit 780c676b733629966efeb4bbaf5a5d88d5b3d23d
Author: R. RyanTM <ryantm-bot@ryantm.com>
Date:   Mon Apr 13 19:26:51 2026 +0000

    obs-cmd: 0.31.3 -> 1.0.0

The bot did the update, but the package doesn't explicit the script:

$ git diff --staged
diff --git a/pkgs/by-name/ob/obs-cmd/package.nix b/pkgs/by-name/ob/obs-cmd/package.nix
index 9e11f3d97c1d..c9b916e2ac93 100644
--- a/pkgs/by-name/ob/obs-cmd/package.nix
+++ b/pkgs/by-name/ob/obs-cmd/package.nix
@@ -2,6 +2,7 @@
+  nix-update-script,
 }:

+  passthru.updateScript = nix-update-script {};
+

By reading the docs it seems that there is a "chain" it follows:

It uses package repository information from Repology.org (though that requires other projects to detect the update), the GitHub releases API, and, if available, the package passthru.updateScript

I remember when I added the change I ran nix-update -A obs-cmd and it updated successfully, even if the bot logs didn't yet pick up the new version.

So maybe it is useful to add it (?)