Adding VersionStream for neo4j-browser-2025.06

[octo-sts]

No description provided.

[octo-sts]

🔄 Build Failed: Git Checkout Error

FAIL Expected commit de7843d8d5d41b1834b40f7c64ed826200d38cb0 for neo4j-2025.06.2, found 6a668a02381ed3c5eed879f21e2c58d14af16c2d

Build Details

Category	Details
Build System	melange
Failure Point	git checkout of tag neo4j-2025.06.2 from https://github.com/neo4j/neo4j-browser

Root Cause Analysis 🔍

The expected commit hash for tag neo4j-2025.06.2 in the package YAML file (de7843d8d5d41b1834b40f7c64ed826200d38cb0) does not match the actual commit hash of that tag in the repository (6a668a02381ed3c5eed879f21e2c58d14af16c2d). This indicates that either the tag has been moved or the expected commit hash in the package definition is incorrect.

---

🔍 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.03 #49517

Suggested Changes

File: neo4j-browser-2025.06.yaml

• replace at line 32 (expected-commit hash in git-checkout section)
  Original:

      expected-commit: de7843d8d5d41b1834b40f7c64ed826200d38cb0

Replacement:

      expected-commit: 6a668a02381ed3c5eed879f21e2c58d14af16c2d

Click to expand fix analysis

Analysis

The build failure is caused by a git tag reference mismatch. The issue is that the expected commit hash (de7843d8d5d41b1834b40f7c64ed826200d38cb0) specified in the package YAML file does not match the actual commit hash (6a668a02381ed3c5eed879f21e2c58d14af16c2d) that the tag neo4j-2025.06.2 points to in the GitHub repository.

Looking at the similar fixed build failure, the same issue occurred with a different Neo4j version. In that case, the fix was to update the expected-commit hash in the YAML file to match the actual commit that the git tag points to. This is a common issue in package build systems that pin specific git commit hashes for reproducibility, but where upstream tags might be moved or updated after the package definition was written.

Click to expand fix explanation

Explanation

The build is failing because the git tag neo4j-2025.06.2 in the Neo4j browser repository now points to commit 6a668a02381ed3c5eed879f21e2c58d14af16c2d, but the package definition expects it to point to commit de7843d8d5d41b1834b40f7c64ed826200d38cb0.

This mismatch can happen for several reasons:

1. The upstream repository maintainers might have changed where the tag points to (force-updated the tag)
2. The package definition might have used an incorrect commit hash initially
3. The tag might have been moved to incorporate a fix or update

The solution is to update the expected-commit value in the YAML file to match the current commit hash that the tag points to. This ensures the build system can verify it's building the correct version and provides reproducibility.

After making this change, the build should succeed because the git-checkout step will correctly verify that the tag points to the expected commit hash. This is the same approach used in the similar fixed build failure example where they updated the expected-commit hash from d00cf0ce1a774d94afc0bdf936e5f789006a3fa5 to 064eeaa9cba2f6cb4c0ded778999962a93777d68.

Click to expand alternative approaches

Alternative Approaches

• Instead of updating the expected-commit hash, we could remove the expected-commit validation entirely, but this would reduce build reproducibility and is not recommended for production packages.
• Another approach would be to pin to the specific commit hash rather than using the tag, but this would make automatic updates more difficult as the update system is configured to look for new tags matching a pattern.
• A third option would be to check with the Neo4j team to see if the tag was moved intentionally and understand why, but for immediate resolution updating the expected hash is the most straightforward fix.

---

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

[AmberArcadia]

Rolling this into a subpackage of #59161