feat: automate pinned upstream workflow refresh - #4
Merged
Merged
Conversation
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
Add explicit upstream tracking metadata and a deterministic refresh path for vendored workflow sources.
The effective source remains immutable: refresh resolves the tracked upstream ref to a full commit SHA, downloads that exact file, recalculates SHA-256, updates the vendored copy, validates the result, and opens a reviewable pull request.
This follows the useful part of Nextcloud's workflow-template synchronization model while preserving this repository's stronger immutable pin + hash boundary.
Details
repository/ref/pathtracking metadata;sync_upstream.py refresh;WORKFLOW_UPDATE_TOKENso generated PRs trigger normal CI;upstream/vendor/.Patch application remains a separate layer and will be implemented independently so upstream refresh and downstream adaptations stay reviewable.