Skip to content

Add Kin registry release automation#2

Open
troyjr4103 wants to merge 1 commit into
mainfrom
ci/registry-release-automation
Open

Add Kin registry release automation#2
troyjr4103 wants to merge 1 commit into
mainfrom
ci/registry-release-automation

Conversation

@troyjr4103

@troyjr4103 troyjr4103 commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Add Kin registry release/dependency-wave automation using firelock-ai/kin-actions@v0.1.1
  • Require release-relevant Cargo source changes to move the package version before merge/publish
  • Publish registry packages idempotently, verify checksum/fresh consumer install, then dispatch downstream dependency-wave PRs
  • Use scoped workflow secrets instead of secrets: inherit

Verification

  • Parsed all changed workflow YAML with Ruby YAML.load_file
  • Ran bash -n for shared shell scripts and python3 -m py_compile for shared Python scripts
  • Ran git diff --check for each repo branch
  • Verified commits include DCO Signed-off-by
  • Fixed and tagged kin-actions@v0.1.1 after the first PR run exposed empty registry-build-command bash handling

@troyjr4103 troyjr4103 force-pushed the ci/registry-release-automation branch from 5c5efaf to f6c3490 Compare June 18, 2026 20:31
Signed-off-by: Troy Fortin <troy@firelock.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant