[*] Chore: Add a post-release action to update the examples#7744
Merged
[*] Chore: Add a post-release action to update the examples#7744
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
zurfyx
approved these changes
Aug 7, 2025
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
2 participants
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
Per #7743 the package-lock files are not updated for examples when a release is published. This is a bit tricky because we can't update them until after the release happens, so it needs to be in a separate PR.
This updated workflow will automatically create a branch after a release is published with updated package-lock files. Like with updating a version, creating the associated PR is a manual process (github won't run actions for an automated PR unless it is using a personal access token).
Test plan
There isn't a lot we can do to test actions like this without releasing them. In order to run it we first need to merge it to the default branch (main). Once the file is in place on main we can iterate on it from a branch if any issues arise.
https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax#onworkflow_dispatch