Repository navigation
research: publish scholarly release v1 from frozen archive lock - #158
Merged
Merged
Conversation
|
Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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
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
Add a one-shot scholarly release workflow for the frozen BPFCompat pilot-v1
research archive.
The workflow is intentionally named
scholarly-release-v1.ymlrather thanresearch-*.yml, so adding it does not modify the already frozenresearch-v1archive payload selection or its committed archive lock.Trigger
The workflow runs only when this workflow file is pushed to
main. Mergingthis PR is therefore the release action.
It does not use a
v*tag, so it does not enter BPFCompat's product releasepipeline.
Release procedure
The job:
research-v1tag or release;research-v1tag at the exact merge commit;Published assets:
archive-manifest.jsonarchive-lock.jsonbpfcompat-research-v1-payload.zipRELEASE-CHECKSUMS.txtEvidence boundary
The release notes explicitly state that this is a reproducibility release of
pilot evidence, not a claim of peer review or institutional endorsement.
This PR does not mint a DOI. Zenodo/DOI remains the next gate after the GitHub
release is successfully published.
Summary by CodeRabbit