chore: sync skills with dockyard#1222
Merged
Merged
Conversation
Contributor
Registry Build PreviewAll registries built successfully! Registry:
|
rdimitrov
approved these changes
May 15, 2026
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.
Dockyard Skill Sync
This PR aligns the OCI tag and git ref of every dockyard-sourced
skill.jsonwith the correspondingskills/<name>/spec.yamlinstacklok/dockyard.
Each scheduled run reads dockyard's
spec.yamlfor every skill whosefirst OCI package targets
ghcr.io/stacklok/dockyard/skills/*andrewrites both the OCI tag (
packages[].identifier) and the upstreamgit ref (
packages[].ref) so the two stay in lockstep with whateverdockyard last published.
This is an automated PR created by the daily skill sync workflow.