Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix workflow #481

Merged
merged 4 commits into from
Dec 4, 2022
+12 −15
Merged

Fix workflow #481

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
cb28bd0
Fix workflow
matt-ramotar Dec 4, 2022
26e5213
Fix workflow
matt-ramotar Dec 4, 2022
de9ed17
Run manually only
matt-ramotar Dec 4, 2022
62ae3d9
Update RELEASING.md
matt-ramotar Dec 4, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 0 additions & 4 deletions .github/workflows/create_swift_package.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,10 +2,6 @@ name: Create Swift Package

on:
workflow_dispatch:
push:
branches: [ main, store5 ]

jobs:
publish:
if: "!endsWith(env.VERSION_NAME, '-SNAPSHOT')"
uses: touchlab/KMMBridgeGithubWorkflow/.github/workflows/[email protected]
23 changes: 12 additions & 11 deletions RELEASING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,22 +3,23 @@ Releasing

1. Change the version in top level `gradle.properties` to a non-SNAPSHOT version.
2. Update the `cocoapods` version in `build.gradle.kts` in `:store`.
3. Update the `CHANGELOG.md` for the impending release.
4. Update the `README.md` with the new version.
5. `git commit -sam "Prepare for release X.Y.Z."` (where X.Y.Z is the new version)
6. `git tag -a X.Y.X -m "Version X.Y.Z"` (where X.Y.Z is the new version)
3. Modify `create_swift_package.yml` workflow to run on `store5` push.
4. Update the `CHANGELOG.md` for the impending release.
5. Update the `README.md` with the new version.
6. `git commit -sam "Prepare for release X.Y.Z."` (where X.Y.Z is the new version)
7. `git tag -a X.Y.X -m "Version X.Y.Z"` (where X.Y.Z is the new version)
* Run `git tag` to verify it.
7. `git push && git push --tags`
8. `git push && git push --tags`
* This should be pushed to your fork.
8. Create a PR with this commit and merge it.
9. Update the top level `build.gradle` to the next SNAPSHOT version.
10. `git commit -am "Prepare next development version."`
11. Create a PR with this commit and merge it.
12. Login to Sonatype to promote the artifacts https://central.sonatype.org/pages/releasing-the-deployment.html
9. Create a PR with this commit and merge it.
10. Update the top level `build.gradle` to the next SNAPSHOT version.
11. `git commit -am "Prepare next development version."`
12. Create a PR with this commit and merge it.
13. Login to Sonatype to promote the artifacts https://central.sonatype.org/pages/releasing-the-deployment.html
* This part is automated. If it fails in CI, follow the steps below.
* Click on Staging Repositories under Build Promotion
* Select all the Repositories that contain the content you want to release
* Click on Close and refresh until the Release button is active
* Click Release and submit
13. Update the sample module's `build.gradle` to point to the newly released version. (It may take ~2 hours for artifact to be available after release)
14. Update the sample module's `build.gradle` to point to the newly released version. (It may take ~2 hours for artifact to be available after release)