build(release): make module releases reproducible and identifiable - #6
Merged
Merged
Conversation
Record published internal module checksums and normalize oapivalidator metadata for standalone release validation. Show the selected module and version bump in release workflow history.
v-byte-cpu
force-pushed
the
build/reproducible-identifiable-module-releases
branch
from
August 30, 2026 18:08
d466547 to
9b96f31
Compare
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.
Why
Dependent modules must resolve published internal versions outside the
workspace. Release history should also identify each selected module
without requiring users to open individual workflow runs.
What Changed