Skip to content

ci: publish records catalog and framework commit SHAs (PLUG-1) - #14

Closed
jothimani-rajendran wants to merge 1 commit into
mainfrom
plug-1-provenance-shas
Closed

jothimani-rajendran wants to merge 1 commit into
mainfrom
plug-1-provenance-shas

Conversation

@jothimani-rajendran

Copy link
Copy Markdown
Collaborator

PLUG-1 (org-plan plan/prerelease-fixes.md): provenance names commits, not refs.

  • publish.yml gains a step that writes generated_from.yaml (catalog and framework: repository, ref, full SHA from git rev-parse HEAD of each checkout) before the dry-run diff, so a dry run shows it.
  • The publish commit message now reads generated: catalog <ref> @ <sha> (framework <ref> @ <sha>).
  • Refs are written JSON-quoted, so a ref with a colon or quote stays valid YAML. Dispatch inputs reach the shell through env only.
  • The file is written at publish time, not by the build, so generated-only neither produces nor compares it.

Checked: workflow parses as YAML; the new step's script run locally against two throwaway git repos wrote valid YAML with the expected SHAs. Not run: the workflow itself (needs a dispatch, release prep).

Sibling PRs with the identical change: codex, devin, cursor, copilot plugin repos.


Generated by Claude Code

publish.yml writes generated_from.yaml with both checkouts' SHAs and
names them in the commit message.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CiuPvvEiB85VM5hMibNC9r

Copy link
Copy Markdown
Collaborator Author

Superseded by #15 (same change, clean commit).


Generated by Claude Code

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