Skip to content

Parse and generate YAML in sync_back.ts#3556

Draft
mbg wants to merge 5 commits intomainfrom
mbg/ts/sync-back-parse
Draft

Parse and generate YAML in sync_back.ts#3556
mbg wants to merge 5 commits intomainfrom
mbg/ts/sync-back-parse

Conversation

@mbg
Copy link
Member

@mbg mbg commented Mar 7, 2026

This is an alternative to #3547 which avoids the regular expressions entirely. It does this by using the yaml library that we already use in sync.ts to:

  • Parse the workflows in .github/workflows to extract the action versions
  • Then parses, updates, and renders the workflow templates in pr-checks/checks

For sync.ts, I have extracted a mapping of action names to versions into a separate file (action-versions.ts) which can easily be re-generated by the sync_back.ts script.

Risk assessment

For internal use only. Please select the risk level of this change:

  • Low risk: Changes are fully under feature flags, or have been fully tested and validated in pre-production environments and are highly observable, or are documentation or test only.

Which use cases does this change impact?

Environments:

  • Testing/None - This change does not impact any CodeQL workflows in production.

How did/will you validate this change?

  • Unit tests - I am depending on unit test coverage (i.e. tests in .test.ts files).
  • End-to-end tests - I am depending on PR checks (i.e. tests in pr-checks).

If something goes wrong after this change is released, what are the mitigation and rollback strategies?

  • Development/testing only - This change cannot cause any failures in production.

How will you know if something goes wrong after this change is released?

  • Other - Please provide details.

Are there any special considerations for merging or releasing this change?

  • No special considerations - This change can be merged at any time.

Merge / deployment checklist

  • Confirm this change is backwards compatible with existing workflows.
  • Consider adding a changelog entry for this change.
  • Confirm the readme and docs have been updated if necessary.

@mbg mbg requested a review from esbena March 7, 2026 00:34
@mbg mbg self-assigned this Mar 7, 2026
@github-actions github-actions bot added the size/L May be hard to review label Mar 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/L May be hard to review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant