fix: include plugin zip hash in release hash files (#213)#426
Merged
joedolson merged 2 commits intorelease_1.3.0from Feb 9, 2026
Merged
fix: include plugin zip hash in release hash files (#213)#426joedolson merged 2 commits intorelease_1.3.0from
joedolson merged 2 commits intorelease_1.3.0from
Conversation
Signed-off-by: Carrie Dils <carriedils@gmail.com>
Contributor
Adds the plugin ZIP file hash to the release hash files (MD5SUMS, SHA1SUMS, SHA256SUMS, SHA384SUMS). The plugin ZIP file created during the release workflow was not being included in the hash verification files. While the plugin hash was available as a GitHub release asset, users couldn't verify the plugin ZIP using the checksum files provided in the release. Modified bin/bundle.sh to: - Auto-detect the plugin version from the plugin header - Auto-detect the repository name from GITHUB_REPOSITORY environment variable - Locate the plugin ZIP file in /tmp (where it's created by the release workflow) - Calculate and append its MD5, SHA1, SHA256, and SHA384 hashes to the respective hash files Fixes #213 Signed-off-by: Shadi Sharaf <shady@sharaf.me>
shadyvb
force-pushed
the
fix/issue-213-plugin-hash
branch
from
ab1fc49 to
8c136b0
Compare
Ipstenu
approved these changes
Feb 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue
Fixes #213
Summary
Adds the plugin ZIP file hash to the release hash files (MD5SUMS, SHA1SUMS, SHA256SUMS, SHA384SUMS).
Problem
The plugin ZIP file created during the release workflow was not being included in the hash verification files. While the plugin hash was available as a GitHub release asset, users couldn't verify the plugin ZIP using the checksum files provided in the release.
Solution
Modified
bin/bundle.shto:GITHUB_REPOSITORYenvironment variable/tmp(where it's created by the release workflow)Testing
The script now checks for the plugin ZIP file before attempting to hash it, and only processes it if it exists. The hashing follows the same pattern as the WordPress bundle zips.
Related
.github/workflows/releases.yml