Add Software Heritage archival on release#4
Merged
Conversation
On release (and via workflow_dispatch), request Software Heritage Save Code Now so each released revision gets a permanent, forge-agnostic SWHID. Dependency-free curl call, best-effort (continue-on-error, never fails the release). Add a Software Heritage badge to the README.
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.
What
Adds
.github/workflows/swh-save.yml: on each GitHub release (and via manualworkflow_dispatch), requests Software Heritage Save Code Now so the released revision gets a permanent, forge-agnostic, ISO/IEC-standard SWHID. Adds a Software Heritage badge to the README.Why
Complements the existing Zenodo deposit (
docker.yml): Zenodo gives a citable release+metadata DOI but is GitHub-only; Software Heritage gives an immutable code identity that also covers GitLab / self-hosted forks. Every new replication then has a durable software anchor for downstream linking (e.g. OpenAIRE).Notes
curlto the SWH API (no unmaintained third-party action), consistent with howdocker.ymlcalls Zenodo.continue-on-error: true— best-effort archival never fails a release.🤖 Generated with Claude Code