chore: automate updating Podfile.lock files #2483
Open
Conversation
This file contains 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
alduzy
force-pushed
the
@alduzy/update-podfile-workflow
branch
from
28f0127 to
51c2df0
Compare
alduzy
force-pushed
the
@alduzy/update-podfile-workflow
branch
from
51c2df0 to
22037c4
Compare
alduzy
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
This PR adds an
after:bumphook to release process that updatesPodfile.lockfiles in the example apps.It adds a release-it config that may be further adjusted to simplify the release process by requiring less manual work.
Test code and steps to reproduce
Run
yarn release-it --dry-runChecklist