Testing new builds

[scotttwittrockcio]

Complete each step to get your pull request merged in. Learn more about the workflow this project uses.

• Assign members of your team to review the pull request.
• Wait for pull request status checks to complete. If there are problems, fix them until you see that all status checks are passing.
• Wait until the pull request has been reviewed and approved by a teammate
• After pull request is approved, and you determine it's ready add the label "Ready to merge" to the pull request and it will automatically be merged.

[github-actions]

Hey, there @scotttwittrockcio 👋🤖. I'm a bot here to help you.

I think the title of this pull request is not in the correct format. Follow the instructions below and then edit the pull request title to a valid format. I'll check again after you make an edit 👍.

This project uses a special format for pull requests titles. Expand this section to learn more (expand by clicking the ᐅ symbol on the left side of this sentence)...

This project uses a special format for pull requests titles. Don't worry, it's easy!

This pull request title should be in this format:

<type>: short description of change being made

If your pull request introduces breaking changes to the code, use this format:

<type>!: short description of breaking change

where <type> is one of the following:

• feat: - A feature is being added or modified by this pull request. Use this if you made any changes to any of the features of the project.

• fix: - A bug is being fixed by this pull request. Use this if you made any fixes to bugs in the project.

• docs: - This pull request is making documentation changes, only.

• refactor: - A change was made that doesn't fix a bug or add a feature.

• test: - Adds missing tests or fixes broken tests.

• style: - Changes that do not effect the code (whitespace, linting, formatting, semi-colons, etc)

• perf: - Changes improve performance of the code.

• build: - Changes to the build system (maven, npm, gulp, etc)

• ci: - Changes to the CI build system (Travis, GitHub Actions, Circle, etc)

• chore: - Other changes to project that don't modify source code or test files.

• revert: - Reverts a previous commit that was made.

Examples:

feat: edit profile photo
refactor!: remove deprecated v1 endpoints
build: update npm dependencies
style: run formatter 

Need more examples? Want to learn more about this format? Check out the official docs.

Note: If your pull request does multiple things such as adding a feature and makes changes to the CI server and fixes some bugs then you might want to consider splitting this pull request up into multiple smaller pull requests.

[github-actions]

Sample app builds 📱

Below you will find the list of the latest versions of the sample apps. It's recommended to always download the latest builds of the sample apps to accurately test the pull request.

---

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 51.82%. Comparing base (8b30804) to head (3907823).
Report is 16 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main     #465      +/-   ##
============================================
+ Coverage     41.98%   51.82%   +9.84%     
- Complexity      259      290      +31     
============================================
  Files            99       96       -3     
  Lines          2320     2570     +250     
  Branches        344      352       +8     
============================================
+ Hits            974     1332     +358     
+ Misses         1247     1135     -112     
- Partials         99      103       +4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[github-actions]

• java_layout: test-new-builds (1731014930)

[github-actions]

📏 SDK Binary Size Comparison Report

No changes detected in SDK binary size ✅

[github-actions]

• kotlin_compose: test-new-builds (1731014939)