Add changelog-sync workflow#259
Draft
yonib05 wants to merge 4 commits into
Draft
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.
Description
Adds a
changelog-sync.ymlworkflow that, on each published release, opens a cross-repo PR intostrands-agents/harness-sdkto update the changelog page (which aggregates releases across the Strands SDKs and lives in harness-sdk).It's a thin caller of the shared
strands-agents/devtools/changelog-release-prcomposite action (see the devtools PR) — all parsing/rendering logic lives there, deterministically, with no logic duplicated here. Also supportsworkflow_dispatchwith abackfillinput for the one-time historical import.Related Issues
Part of the Strands changelog feature (harness-sdk site PR + devtools action PR).
Type of Change
New feature
Testing
v0.2.1).Notes for reviewers
secrets.CHANGELOG_PR_TOKEN) is a placeholder pending confirmation. The evals job's owngithub.tokencan't open a PR on harness-sdk; this needs a token withpull-requests:write+contents:writeon harness-sdk. Please point me at the org's existing cross-repo automation token to reuse rather than provisioning a new secret.