ScriptHookVDotNet publishes four consecutive nightly CI releases Feb 23-26

ScriptHookVDotNet published a rapid sequence of nightly CI releases across Feb 23–26, 2026, with tags v3.7.0-nightly.99, v3.7.0-nightly.101, v3.7.0-nightly.102 and v3.7.0-nightly.103. The releases appear on the repository path scripthookvdotnet/scripthookvdotnet-nightly, which the project describes simply as "Mirror for CI builds."

The mirror page explains how the nightlies are produced: "Nightly gets an update for a release every commit pushed on the main repository." That behavior aligns with the late-February burst of tags, tying each nightly artifact back to activity in the main ScriptHookVDotNet repository rather than to edits on the mirror itself.

The mirror also enforces an artifact immutability policy for recent nightlies. The repository text states, "Starting from v3.7.0-nightly.48, binary archives/artifacts will not be modified once releases are published." The mirror further cautions that "Although immutable releases can be deleted, tags that are already used by ones cannot be recreated. Therefore, you can always obtain the same archive with the same version tag unless the release associated with the tag is deleted."

That linkage and immutability affect how modders and developers trace issues. The mirror clarifies commit-hash mechanics: "Commit SHAs on tags are not important for artifacts on this nightly repository, as they only reference commits on this nightly repository, which is rarely updated by commits." It adds that "The link in a release description refers to a commit in the main repository" and that "The description in each release contains the short and full hashes of the corresponding commit in the main repository." For reporting problems the page instructs, "When you report bugs in the main repository, report with a commit in the main repository, not a commit in this repository," and explains that "Reporting bugs with the short commit hash is acceptable unless the main branch in the main repository contains multiple hashes starting with the short commit hash (you could report with the full hash in this case)."

The mirror's UI fragments captured alongside the releases show repository metadata and a couple of page issues. The page lists "## Releases 245" and "## Packages 0" under repository stats, and navigation fragments include "README.md" and a repeated "History7 Commits 7 Commits" line. The capture also contains the error text "There was an error while loading. Please reload this page." appearing more than once.

One detail the mirror capture does not show is v3.7.0-nightly.100; the supplied fragments list .99 and .101–.103 without .100. Unanswered items remain: exact publish timestamps and publisher identities for v3.7.0-nightly.99, .101, .102 and .103, whether v3.7.0-nightly.100 was published or skipped, and whether any of the named artifacts have been deleted since publication.

The immediate takeaway is procedural: nightlies on scripthookvdotnet/scripthookvdotnet-nightly are produced on every main-repo commit, and from v3.7.0-nightly.48 onward the project treats binary archives as immutable once published, so retrieving a given tag should yield the same archive unless that release was deleted.