fix: rewrite 0.3.0 manifest entries to point at archives, not .sha256 files#84
Merged
liamcervante merged 1 commit intopublishedfrom May 6, 2026
Merged
Conversation
… files The 0.3.0 entries for all four plugins had URLs/names ending in .sha256, with the SHA being the digest of the .sha256 text file rather than the archive. This rewrites every 0.3.0 artifact entry with the correct archive URL/name and the archive's actual sha256 (read from the .sha256 file's contents).
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
1 participant
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.
Summary
The 0.3.0 entries for all four plugins (
infracost-parser-plugin,infracost-provider-plugin-aws,infracost-provider-plugin-azurerm,infracost-provider-plugin-google) had URLs and names ending in.sha256, with the recordedshabeing the digest of the .sha256 text file rather than the archive itself. The bug intools/update-manifestis fixed in #83 — this PR fixes the published manifest content directly so existing CLI installs can resolve plugins again without waiting for a re-release.Each entry now points at the actual
.tar.gz/.zip, with the archive's sha256 read from the contents of the corresponding.sha256file.