Adding VersionStream for neo4j-2026.01

[octo-sts]

No description provided.

[octo-sts]

🔄 Build Failed: Git Checkout Error

Expected commit 92013cbcc997b8b349ec385c5b1d734f9d9df496 for 2026.01.4, found 158612c97a5b676d6129396ad0c4d5b772c7c2a4

Build Details

Category	Details
Build System	Melange
Failure Point	git checkout step during source retrieval from https://github.com/neo4j/neo4j

Root Cause Analysis 🔍

The git tag '2026.01.4' points to a different commit than expected in the package configuration. The package expects commit 92013cbcc997b8b349ec385c5b1d734f9d9df496 but the actual commit for this tag is 158612c97a5b676d6129396ad0c4d5b772c7c2a4. This indicates the upstream repository tag was either updated/recreated or the package configuration has an incorrect expected commit hash.

---

🔍 Build failure fix suggestions

Found similar build failures that have been fixed in the past and analyzed them to suggest a fix:

Similar PRs with fixes

• Adding VersionStream for neo4j-2025.08 #65537
• Adding VersionStream for neo4j-2025.03 #49517

Suggested Changes

File: neo4j-2026.01.yaml

• update at line 44 (pipeline section, git-checkout step)
  Original:

expected-commit: 92013cbcc997b8b349ec385c5b1d734f9d9df496

Replacement:

expected-commit: 158612c97a5b676d6129396ad0c4d5b772c7c2a4

Content:

Update the expected-commit hash to match the actual commit that tag 2026.01.4 points to

Click to expand fix analysis

Analysis

Based on the three similar fixes, the consistent pattern is updating the expected-commit hash in the git-checkout step to match the actual commit hash that the Git tag points to in the upstream repository. In all cases, the fix involved replacing the old expected-commit value with the new one that was found during checkout. This indicates that upstream repositories occasionally update their tags to point to different commits, requiring the build configuration to be updated accordingly.

Click to expand fix explanation

Explanation

This fix should work because the error message clearly indicates that the Git tag '2026.01.4' currently points to commit 158612c97a5b676d6129396ad0c4d5b772c7c2a4, but the build configuration expects commit 92013cbcc997b8b349ec385c5b1d734f9d9df496. By updating the expected-commit value to match the actual commit hash, the git-checkout step will succeed. This is the same fix pattern used in all three similar cases where upstream Git tags were updated to point to different commits than originally expected. The fix ensures the build system can successfully checkout the correct commit associated with the specified tag.

Click to expand alternative approaches

Alternative Approaches

• Verify the tag integrity by checking if the upstream repository moved the tag intentionally or if there was an error in the original expected-commit configuration
• Remove the expected-commit validation entirely if frequent tag updates are expected, though this reduces build reproducibility
• Use a specific commit hash instead of a tag reference to avoid future tag movement issues

---

Was this comment helpful? Please use 👍 or 👎 reactions on this comment.