Release v5.1.0 #475
Merged
Release v5.1.0 #475
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
* chore: Upgrade to react-native v0.62.2 (apart from .xcodeproj) * Update ios project to RN62 * Update XCode project settings * Add Swift bridging header for iOS * Add library search paths for ios * Update deps (apart from expo-unimodules) * Update expo-unimodules * chore: Update to detox 16.2.0 (fixes test failing)
* chore: fix typo in .gitattributes * chore: Upgrade to react-navigation@4 * chore: Update react-navigation stack and tabs to v2 * chore: Update flow typedefs
The version number in package.json is not updated when we release internal builds, so it does not make sense to use it as a version name
* feat: Update ICCA intro screens and presets * Add internal build for ICCA * fix: Update intro screens for react-navigation v4 * fix: Fix background color for additional info screens in intro * Add script to start ICCA variant in debug mode * Update icca intro screens * Update to latest ICCA presets
* New translations en.json (Thai) * New translations en.json (Thai) * New translations en.json (Thai) * New translations en.json (Thai) * New translations en.json (Nepali) * New translations en.json (Nepali)
* release/v2.1.0: (53 commits) fix: Turn off dev mode (yellow warning boxes) in universal build chore: Roll back to react-native-mapbox-gl/[email protected] chore: Update KNOWN_ISSUES for v5.0.0 release chore: Update changelog (prepare for release) fix: Update Thai and Nepali translations fix: Update Portuguese translations fix: Fix observations not rendering when GPS is off (#431) fix: Ensure sync errors are always propagated to frontend. chore: Update to [email protected] chore: Update package-lock to v5.0.0 chore(deps): bump to @mapeo/core v8.3.2 for missing data fixes fix: ignore missing data errors and errors that are stale chore: ensure flow understands we use select_multiple now too fix: some last fixes for mapeo alerts chore: for flow, ensure fields and preset are always present fix: Improve the formatting of Mapeo Alerts fixes #401 fix: 'missing data' error will not cancel large syncs too early fix: Ignore errors (e.g., ECONNABORTED) that are now caught by the 'connected' property fix: When WiFi connection state changes, refresh peer list fix: show a yellow icon when disconnected ... # Conflicts: # messages/pt.json # package-lock.json # package.json # src/backend/package-lock.json # src/backend/package.json # src/frontend/screens/SyncModal/index.js
* hotfix/v5.0.1: chore: Update CHANGELOG and bump version fix: Disable dev mode in Google Play app bundle
* hotfix/v5.0.2: chore: Attempt to fix Google Play deploy (send correct aab file) chore: Fix bitrise build so that the version name is correct on release
* hotfix/v5.0.3: chore: Update changelog fix: Bump version number
This leads to cleaner diffs and easier code manipulation https://medium.com/@nikgraf/why-you-should-enforce-dangling-commas-for-multiline-statements-d034c98e36f8
* feat: Create ICCAs build scripts & exclude ICCA screens from main build Use Metro build config to conditionally include ICCA screens so that ICCA resouces are not included in the main Mapeo build. This avoids the images used in the ICCAs intro screens increasing the file size of the main Mapeo APK. * feat: Ship apk variants with only the presets they need Choose the presets that are included in the apk at build time instead of runtime. This reduces the apk size and removes runtime code for conditionally running code based on app variant. * chore: Patch react-native so gradle tasks package ICCA variant Adds the app variant name as an environment variable in the gradle build script so that metro bundler can package JS files according to variant by using the `sourceExts` option.
#448) * feat: Add empty offline map so that points still show if no custom map * fix: Keep assets folder in git * chore: Cleanup code * fix: fix offline fallback mapstyle for inset map of observation view Also refactors the useStyleURL hook to be more explicit
Uses the translations.json file included in a mapeo config folder to translate preset names (e.g. category names that appear on the "choose what is happening" screen), field labels (e.g. Questions) and placeholders, and select field options.
* feat: Add "About Mapeo" page in settings screen with app version * Add e2e tests
It seems like in e2e tests the detox tap() is too fast for RNGH to register, causing button taps to fail: software-mansion/react-native-reanimated#596
…dit (#472) * chore: use react-native touchables in tests (RNGH = flaky tests) It seems like in e2e tests the detox tap() is too fast for RNGH to register, causing button taps to fail: software-mansion/react-native-reanimated#596 * fix: Show "discard edits" not "discard observation" when cancelling edit fixes #381 * add tests * fix crash in test
* New translations en.json (French) * New translations en.json (Spanish) * New translations en.json (Vietnamese) * New translations en.json (Portuguese, Brazilian) * New translations en.json (Indonesian) * New translations en.json (Khmer) * New translations en.json (Thai) * New translations en.json (Hindi) * New translations en.json (Malay) * New translations en.json (Burmese) * New translations en.json (Swahili, Kenya) * New translations en.json (Nepali) * New translations en.json (Lao) * New translations en.json (Portuguese, Brazilian) * New translations en.json (Thai) * New translations en.json (Thai) * New translations en.json (Vietnamese) * New translations en.json (French) * New translations en.json (Spanish) * New translations en.json (Vietnamese) * New translations en.json (Portuguese, Brazilian) * New translations en.json (Indonesian) * New translations en.json (Khmer) * New translations en.json (Thai) * New translations en.json (Hindi) * New translations en.json (Malay) * New translations en.json (Burmese) * New translations en.json (Swahili, Kenya) * New translations en.json (Nepali) * New translations en.json (Lao) * New translations en.json (Portuguese, Brazilian) * New translations en.json (Thai) * New translations en.json (Thai) * New translations en.json (French) * New translations en.json (Spanish) * New translations en.json (Vietnamese) * New translations en.json (Portuguese, Brazilian) * New translations en.json (Indonesian) * New translations en.json (Khmer) * New translations en.json (Thai) * New translations en.json (Hindi) * New translations en.json (Malay) * New translations en.json (Burmese) * New translations en.json (Swahili, Kenya) * New translations en.json (Nepali) * New translations en.json (Lao) * New translations en.json (Spanish) * New translations en.json (Vietnamese) * New translations en.json (Vietnamese)
gmaclennan
requested review from
okdistribute,
TomRFPP,
aliya-ryan and
jencastrodoesstuff
* New translations en.json (Thai) * New translations en.json (Spanish)
* New translations en.json (Thai) * New translations en.json (Spanish) * New translations en.json (German) * New translations en.json (German) * New translations en.json (German) * New translations en.json (Khmer) * New translations en.json (Khmer)
jencastrodoesstuff
approved these changes
Oct 20, 2020
|
We discussed this on our Dd team call (2020-10-20) and agreed that this is ready for release based on @jencastrodoesstuff's in-depth testing. We are going to release despite only having one approval so far. |
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.
This PR is to prepare for Mapeo Mobile release v5.1.0. No more features will be added to v5.1.0 at this time, only bug fixes. You can download the APK for testing below:
Any bugs found testing the Release Candidate should be filed as an issue. If the bug is considered "blocking" (i.e. we should not release v5.1.0 until it is fixed) then link the issue to the project Mapeo Mobile v5.1. When all bugs in the project are fixed and reviewers have approved this PR, then v5.1 will be released and published to the Play Store and made available to download on our website.
See the draft changelog for changes since our last public release (v5.0.3).
Feature highlights in this version, which are particularly important for new Mapeo users: