-
Notifications
You must be signed in to change notification settings - Fork 38
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Monorepo support (#37) * Upgrade to expo 50 sdk * Upgrade morrowdigital/watermelondb-expo-plugin * Add Android monorepo support * Add ios monorepo support - Adds monorepo support to ios - Removes unnecessary pods as they are already auto-linked * Remove unused code * Remove duplicated bridgingHeader Expo 50 there is already an empty .swift file for this * Add monorepo support * apply changes to build * bump version 2.3.2-beta.0 * Chore/docs update (#38) * add changelog and contributions * maintainer's guide * Chore/GitHub actions (#39) * 2.3.2-beta.1 * add pushing back to repo * remove dry-run * github actions / add beta action * chore/fix git push * remove version bump * add Environment again * add version bumping * removed version upgrade * added npm token placeholder * different npm token in previous step * add yarn gha * more places for NPM_TOKEN * Chore/update docs on gha (#40) * update docs and npmrc * update releaes gha * bugfix/revert test code * 2.3.2 * update CHANGELOG.md --------- Co-authored-by: Carlos Moreno <[email protected]>
- Loading branch information
1 parent
f48c1ff
commit 9972e43
Showing
12 changed files
with
1,398 additions
and
1,149 deletions.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -8,41 +8,34 @@ on: | |
jobs: | ||
publish: | ||
runs-on: ubuntu-latest | ||
# environment: | ||
# name: Beta | ||
environment: | ||
name: Beta | ||
steps: | ||
- name: Checkout code | ||
uses: actions/checkout@v4 | ||
with: | ||
persist-credentials: false | ||
ref: beta | ||
|
||
- name: Setup npmrc | ||
run: echo "//registry.npmjs.org/:_authToken=${{ secrets.NPM_TOKEN }}" > ~/.npmrc | ||
|
||
- name: Setup Node.js | ||
uses: actions/setup-node@v2 | ||
uses: actions/setup-node@v3 | ||
with: | ||
node-version: 20 | ||
|
||
- name: Install dependencies | ||
run: yarn install | ||
uses: borales/actions-yarn@v4 | ||
with: | ||
cmd: install | ||
env: | ||
NPM_TOKEN: ${{ secrets.NPM_TOKEN }} | ||
|
||
|
||
- name: Build and publish | ||
- name: Publish | ||
run: | | ||
yarn run build | ||
npm version prerelease --preid=beta | ||
npm publish --tag beta --dry-run | ||
npm publish --tag beta | ||
env: | ||
NPM_TOKEN: ${{ secrets.NPM_TOKEN }} | ||
# | ||
# - name: Prepare Git | ||
# uses: actions/checkout@v4 | ||
# with: | ||
# persist-credentials: false | ||
# | ||
# - name: Push changes | ||
# run: | | ||
# git config user.name "GitHub Actions" | ||
# git config user.email "[email protected]" | ||
# git add . | ||
# git commit -m "Bump version and publish beta package" | ||
# git push origin HEAD:beta | ||
|
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
name: Publish Production Package | ||
|
||
on: | ||
workflow_dispatch: | ||
branches: | ||
- main | ||
|
||
jobs: | ||
publish: | ||
runs-on: ubuntu-latest | ||
environment: | ||
name: Production | ||
steps: | ||
- name: Checkout code | ||
uses: actions/checkout@v4 | ||
with: | ||
persist-credentials: false | ||
ref: beta | ||
|
||
- name: Setup npmrc | ||
run: echo "//registry.npmjs.org/:_authToken=${{ secrets.NPM_TOKEN }}" > ~/.npmrc | ||
|
||
- name: Setup Node.js | ||
uses: actions/setup-node@v3 | ||
with: | ||
node-version: 20 | ||
|
||
- name: Install dependencies | ||
uses: borales/actions-yarn@v4 | ||
with: | ||
cmd: install | ||
env: | ||
NPM_TOKEN: ${{ secrets.NPM_TOKEN }} | ||
|
||
|
||
- name: Publish | ||
run: | | ||
npm publish --tag latest | ||
env: | ||
NPM_TOKEN: ${{ secrets.NPM_TOKEN }} | ||
|
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -84,3 +84,4 @@ android/ | |
!.yarn/sdks | ||
!.yarn/versions | ||
|
||
.npmrc |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,10 @@ | ||
# CHANGELOG | ||
## [2.3.2] - 29/3/2024 | ||
### Added | ||
- Monorepo support | ||
- Documentation for Maintainers and Contributors | ||
- Github actions for Publishing Beta and Release | ||
|
||
|
||
## [2.3.1] - 21/3/2024 | ||
|
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
# Contributing to `watermelondb-expo-plugin` | ||
|
||
Thank you for your interest in contributing to `watermelondb-expo-plugin`! We appreciate your help in making our project better. | ||
|
||
## Getting Started | ||
|
||
To contribute to this project, follow these steps: | ||
|
||
1. **Fork** the repository by clicking on the "Fork" button at the top right corner of this page. This will create a copy of the repository in your GitHub account. | ||
|
||
2. **Clone** your forked repository to your local machine: | ||
|
||
3. **Make** update and changes to the codebase. | ||
|
||
## Create a Pull Request | ||
|
||
Submit a **Pull Request** to the `beta` branch of the original repository. | ||
|
||
* Ensure that your changes are made to the beta branch of your forked repository. | ||
* Submit your pull request (PR) from the branch where you made your changes to the beta branch of the original repository. | ||
* Provide a clear and descriptive title for your PR and include any relevant information about the changes you've made. | ||
|
||
## Code Review | ||
Once your pull request is submitted, it will undergo review by project maintainers. We appreciate your patience during this process and welcome any feedback or suggestions for improvement. | ||
|
||
Thank you for your contributions! |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,40 @@ | ||
# MAINTAINER'S GUIDE | ||
|
||
## Gitflow | ||
|
||
* `main`: branch is used for production releases. | ||
* `beta`: branch is used for beta testing. It is gathering all the code from bug fixes and new features. | ||
* `chore/*`: documentation updates, and maintenance tasks. | ||
* `feature/*`: new features. | ||
* `fix/*`: bug fixes. | ||
|
||
## Versioning | ||
|
||
We use semantic versioning. | ||
|
||
### Beta versions | ||
|
||
Before we release a new version, we first release one or more series of `beta` versions. | ||
|
||
For example if the current production version is 1.0.1, and we want to move on with releasing 1.0.2, first we release 1.0.2-beta.1, 1.0.2-beta.2, etc. until we are confident that the new version is stable. | ||
|
||
To release a beta: | ||
1. Update the CHANGELOG.md file with the latest beta version and release date of the version. | ||
2. bump the version in `package.json>version` with `yarn bump:beta` | ||
3. Push the changes to the `beta` branch. | ||
4. Then release by triggering the GitHub Actions workflow `Publish Beta Package` on the `beta` branch. | ||
|
||
## Production releases | ||
|
||
When we are confident that the beta version is stable, we release a production version. | ||
|
||
1. In `beta` branch bump the version in `package.json>version` to the new version with `yarn bump:release` (or manually). | ||
2. Update the CHANGELOG.md file with the new version and release date of the version. The changes that were previously in beta should be moved to the new version. | ||
3. Push the changes to beta. | ||
4. Create a PR and merge `beta` to `main`. | ||
5. Then release by triggering the Github action `Publish Production Package` on `main` branch. | ||
|
||
|
||
> Note: The Github actions need approval to be launched. If you're part of the admins team, you can do it yourself. | ||
|
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
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
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
Oops, something went wrong.