Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding VersionStream for gitlab-pages-17.7 #38365

Merged
merged 3 commits into from
Dec 30, 2024
Merged

Adding VersionStream for gitlab-pages-17.7 #38365

merged 3 commits into from
Dec 30, 2024

Conversation

octo-sts[bot]
Copy link
Contributor

@octo-sts octo-sts bot commented Dec 26, 2024

No description provided.

Copy link
Contributor Author

octo-sts bot commented Dec 26, 2024

Gen AI suggestions to solve the build error:

• Detected Error: "FAIL Expected commit 2b0a27333cea5588b341f49e1ca725a48fd3b9f3 for v17.7.0, found 569f674d03376d05a85081ede8e6d54931060b2f"

• Error Category: Version/Commit Hash Mismatch

• Failure Point: git-checkout step in pipeline

• Root Cause Analysis: The expected commit hash in the YAML file doesn't match the actual commit hash for the v17.7.0 tag in the GitLab Pages repository

• Suggested Fix: Update the expected-commit hash in the git-checkout step:

  - uses: git-checkout
    with:
      repository: https://gitlab.com/gitlab-org/gitlab-pages.git
      tag: v${{package.version}}
      expected-commit: 569f674d03376d05a85081ede8e6d54931060b2f

• Explanation: The build is failing because Melange's integrity check found a mismatch between the specified commit hash and the actual commit hash for the v17.7.0 tag. This is a security feature to ensure the source code hasn't been tampered with. Updating to the correct commit hash will allow the build to proceed.

• Additional Notes:

  • This is a common issue when updating package versions
  • The commit hash can be verified on GitLab's repository page
  • Always verify the commit hash when updating package versions
  • The hash mismatch indicates either:
    1. The tag was moved
    2. The wrong commit hash was specified
    3. The package version was updated without updating the commit hash

• References:

Signed-off-by: Jason Hall <jason@chainguard.dev>
@imjasonh imjasonh enabled auto-merge (squash) December 30, 2024 18:44
@octo-sts octo-sts bot added the bincapz/pass bincapz/pass Bincapz (aka. malcontent) scan didn't detect any CRITICALs on the scanned packages. label Dec 30, 2024
@imjasonh imjasonh merged commit fcfc3b5 into main Dec 30, 2024
20 of 21 checks passed
@imjasonh imjasonh deleted the gitlab-pages-17.7 branch December 30, 2024 18:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automated pr bincapz/pass bincapz/pass Bincapz (aka. malcontent) scan didn't detect any CRITICALs on the scanned packages. service:version-stream
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants