feat: append random suffix to vlt registry auth token per iteration#55
Merged
lukekarrys merged 1 commit intovltpkg:mainfrom Mar 5, 2026
Merged
Conversation
Appends a colon-separated random hex string to VLT_REGISTRY_AUTH_TOKEN in the --prepare step for each hyperfine iteration. This ensures every benchmark run uses a unique token, preventing the registry from serving cached responses across iterations. The suffix is generated at prepare-time via /dev/urandom (32 hex chars), so each iteration gets a different value. The actual token remains the prefix, with the random part appended after a colon separator.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
When benchmarking
registry.vlt.io, appends a random suffix to theVLT_REGISTRY_AUTH_TOKENfor every hyperfine iteration. The suffix is separated from the actual token with a colon (:) and is different for each run.How it works
The
BENCH_SETUP_REGISTRY_VLTprepare command now writes the auth token as:The random part is generated at prepare-time (before each timed run) via:
head -c 16 /dev/urandom | xxd -pThis produces 32 hex characters that are unique per iteration, ensuring the registry does not serve cached responses across benchmark runs.
Example
Changes
scripts/registry/common.sh:$(random)to vlt auth token in prepare stepOnly the vlt registry token is modified — npm and AWS registries are unchanged.