Update API level to target Android 14 (API level 34). #26
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
# Conflicts: # build.gradle # data/src/main/java/io/github/turskyi/data/datasources/local/firestore/FirestoreDatabaseSourceImpl.kt # gradle.properties # presentation/build.gradle # presentation/src/main/java/io/github/turskyi/travellingpro/features/flags/view/fragments/FlagFragment.kt # presentation/src/main/java/io/github/turskyi/travellingpro/features/home/view/ui/AddCityDialogFragment.kt # presentation/src/main/java/io/github/turskyi/travellingpro/features/home/view/ui/HomeActivity.kt # presentation/src/main/res/layout/activity_traveller.xml # presentation/src/main/res/layout/activity_travellers.xml # presentation/src/main/res/values/dimens.xml
- Update build status badge in README.md - Add Google Play badge to README.md - Update build.gradle to version 2.1.1 - Update Gradle wrapper distributionUrl to version 8.2-all.zip - Refactor FirestoreDatabaseSourceImpl.kt for better readability - Update GitHub Actions workflow to ignore master branch for pushes Signed-off-by: Dmytro Turskyi <dmytro.turskyi@gmail.com>
…in workflow steps Updated the JDK version to 17 in the workflow setup and corrected capitalization in the steps for generating and uploading the release APK. Also added the serviceCredentialsFile for Firebase App Distribution. Signed-off-by: Dmytro Turskyi <dmytro.turskyi@gmail.com>
Signed-off-by: Dmytro Turskyi <dmytro.turskyi@gmail.com>
Signed-off-by: Dmytro Turskyi <dmytro.turskyi@gmail.com>
# Conflicts: # build.gradle # data/src/main/java/io/github/turskyi/data/datasources/local/firestore/FirestoreDatabaseSourceImpl.kt
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 3579767 | Triggered | Facebook App Keys | b1b5fa8 | presentation/src/main/res/values/strings.xml | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
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.
No description provided.