Skip to content

release: no SHA256SUMS, no checksum step in the docs (#66) - #67

Merged
compot-dev merged 1 commit into
masterfrom
release/no-sha256sums
Oct 17, 2026
Merged

compot-dev merged 1 commit into
masterfrom
release/no-sha256sums

Conversation

@compot-dev

Copy link
Copy Markdown
Collaborator

Closes #66.

  • build.yml: the release job no longer writes SHA256SUMS; the release notes and the header comment stop listing it.
  • READMEs (all three): SHA256SUMS is gone from the "Permanent links" table, the download example (curl only) and the release steps.
  • Unchanged, internal to the build: the pinned checksum of the downloaded toolchain (ci/build-musl.sh). The CHANGELOG.md history keeps what 3.0.2 shipped.

Workflow and docs only: no version bump.

Users need not check the downloaded files against checksums: the
release job no longer writes SHA256SUMS, and the release notes and the
build.yml header stop listing it. READMEs: SHA256SUMS is gone from the
permanent-links table, the download example and the release steps.
The pinned checksum of the downloaded toolchain (ci/build-musl.sh) stays.

Closes #66
@qodo-free-for-open-source-projects

Copy link
Copy Markdown

PR Summary by Qodo

Stop publishing SHA256SUMS and remove checksum instructions

⚙️ Configuration changes 📝 Documentation 🕐 10-20 Minutes

Grey Divider

AI Description

• Stop generating SHA256SUMS for the latest release and remove it from release notes.
• Update all three READMEs to list only published assets and show a download-only example.
• Keep the build's toolchain checksum verification unchanged.
Diagram

graph TD
  A["Build artifacts"] --> B["Release packaging"] --> C["Latest release"] --> D["Downloaders"]
  E["Localized READMEs"] -->|show download steps| D
  E -->|list published assets| C
Loading
High-Level Assessment

Removing manifest generation and updating every current download instruction is the direct way to align documentation with the release assets. The separate checksum verification for downloaded build toolchains remains in place.

Files changed (4) +8 / -15

Documentation (3) +6 / -12
README.mdDocument direct downloads in English +2/-4

Document direct downloads in English

• Removes SHA256SUMS from the permanent-links table and release steps. The example downloads only the binary, without a checksum command.

README.md

README.ru.mdDocument direct downloads in Russian +2/-4

Document direct downloads in Russian

• Removes SHA256SUMS from the permanent-links table and release steps. The example downloads only the binary, without a checksum command.

README.ru.md

README.zh-CN.mdDocument direct downloads in Chinese +2/-4

Document direct downloads in Chinese

• Removes SHA256SUMS from the permanent-links table and release steps. The example downloads only the binary, without a checksum command.

README.zh-CN.md

Other (1) +2 / -3
build.ymlRemove the release checksum manifest +2/-3

Remove the release checksum manifest

• Stops generating and checking SHA256SUMS when assembling release assets. Removes references to the manifest from the workflow header and published release notes.

.github/workflows/build.yml

@qodo-free-for-open-source-projects

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Grey Divider

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Grey Divider

Tip of the day
💡 Did you know, you can see how risky a PR is at a glance with blast radius labels

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

Grey Divider

Qodo Logo

@compot-dev
compot-dev merged commit 8aa1ba2 into master Oct 17, 2026
17 checks passed
@compot-dev
compot-dev deleted the release/no-sha256sums branch October 17, 2026 23:09
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.

Release: no SHA256SUMS, no checksum step in the docs

1 participant