Automated Spec Update#549
Closed
dropbox-sdk-updater[bot] wants to merge 1 commit into
Closed
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #549 +/- ##
=======================================
Coverage 65.19% 65.19%
=======================================
Files 34 34
Lines 65205 65205
Branches 4642 4642
=======================================
Hits 42508 42508
Misses 22536 22536
Partials 161 161
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
735a331613b476c6ed0670c8746075315eb6905e c6ab6b6b4feda087241fa377e5d14a84cd3c7092 Use AWS Secrets Manager + GitHub App installation tokens instead of a classic personal access token. Scoped to dropbox-sdk-python initially. 4a5fa1405ff0b7b5b388eedbbc02a72dd7956ff4 Group all GitHub Actions updates into one PR 7e5f66814d44d53f76b30049068bfb1ca27a0799 This updates the spec dispatch workflow to use `peter-evans/repository-dispatch@v4` instead of the older v1 action. The workflow still dispatches the same `spec_update` event to the existing downstream repositories, but now explicitly disables default `GITHUB_TOKEN` permissions because remote dispatches are authenticated with `SPEC_UPDATE_TOKEN`. This also sets `fail-fast: false` for the repository matrix so one failed downstream dispatch does not cancel the remaining dispatch attempts, and adds a small `client-payload` containing the source repository, ref, and commit SHA for downstream workflows that want to inspect where the spec update came from.
dropbox-sdk-updater
Bot
force-pushed
the
spec_update_2026_07_17
branch
from
July 17, 2026 18:44
9876ce6 to
558a69b
Compare
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.
Automated Spec Update
735a331613b476c6ed0670c8746075315eb6905e
c6ab6b6b4feda087241fa377e5d14a84cd3c7092
Use AWS Secrets Manager + GitHub App installation tokens instead of
a classic personal access token. Scoped to dropbox-sdk-python initially.
4a5fa1405ff0b7b5b388eedbbc02a72dd7956ff4
Group all GitHub Actions updates into one PR
7e5f66814d44d53f76b30049068bfb1ca27a0799
This updates the spec dispatch workflow to use
peter-evans/repository-dispatch@v4instead of the older v1 action. The workflow still dispatches the samespec_updateevent to the existing downstream repositories, but now explicitly disables defaultGITHUB_TOKENpermissions because remote dispatches are authenticated withSPEC_UPDATE_TOKEN.This also sets
fail-fast: falsefor the repository matrix so one failed downstream dispatch does not cancel the remaining dispatch attempts, and adds a smallclient-payloadcontaining the source repository, ref, and commit SHA for downstream workflows that want to inspect where the spec update came from.