Open Isabellakuang opened 1 year ago
I also was facing this, i suggest do this on your local system. Make a habit to bump up the version before doing any "release" git commit. Just read the pkg most of your doubt might get resolved by itself. have a look at this pacakge cider pkg
what do i mean by "release" git commit? - well if you are making a commit with the intention to make the build from it and publish. That is a release git commit according to me.
I am open for suggestion. If someone has better idea.
Hello @Isabellakuang
I'm using other actions to achieve this, and it works great. I use git tags to name the version, and the commit number as build number.
These steps code should be placed before build step, watch out for "fetch-depth: 0"
Check if it makes sense to you!
- name: Check out Git repository
uses: actions/checkout@v2
with:
fetch-depth: 0
- name: Extract version from tag
uses: damienaicheh/extract-version-from-tag-action@v1.0.0
- name: Update Info.plist
uses: damienaicheh/update-ios-version-info-plist-action@v1.0.0
with:
info-plist-path: "ios/YOUR_PROJECT_NAME/Info.plist"
bundle-version: ${{ env.NUMBER_OF_COMMITS }}
bundle-short-version-string: "${{ env.MAJOR }}.${{ env.MINOR }}.${{ env.PATCH }}"
print-file: true
we want to use this action to build ios package and successfully. but when we upload the package the response from Testflight said the version need to update. how to automation update the build version?