Skip to content

use sha256 instead of sha1 for releases#571

Merged
jochenehret merged 5 commits into
cloudfoundry:mainfrom
sap-contributions:sha256
Sep 30, 2025
Merged

use sha256 instead of sha1 for releases#571
jochenehret merged 5 commits into
cloudfoundry:mainfrom
sap-contributions:sha256

Conversation

@dtasSap

@dtasSap dtasSap commented Sep 15, 2025

Copy link
Copy Markdown
Contributor

Use Sha256 instead of Sha1 in releases

@dtasSap dtasSap force-pushed the sha256 branch 3 times, most recently from ea11d05 to 6151718 Compare September 16, 2025 06:38
value:
name: no-stemcell-section
sha1: 5ee0dfe1f1b9acd14c18863061268f4156c291a4
sha1: sha256:5ee0dfe1f1b9acd14c18863061268f4156c291a4

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is actuall too short for a SHA-256 value. Can you adapt the tests with longer test values to avoid confusion between SHA-1 and SHA-256 values?

value:
name: release1
sha1: original-release1-sha1
sha1: sha256:original-release1-sha1

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These test values should be renamed to original-release1-sha256 to avoid confusion. I know, it's just cosmetics...

@dtasSap dtasSap requested a review from jochenehret September 29, 2025 07:22
url: original-inert-release-url
version: original-inert-release-version
sha1: original-inert-release-sha1
sha1: sha256:original-inert-release-sha1

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This and the following test values should also be renamed to "-sha256"

@jochenehret jochenehret self-requested a review September 29, 2025 11:10
@jochenehret jochenehret merged commit 88186c3 into cloudfoundry:main Sep 30, 2025
11 checks passed
@dtasSap dtasSap deleted the sha256 branch October 1, 2025 08:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants