Release 6.0.0-alpha.1

[gdeluna-branch]

Reference

SDK-XXX -- <TITLE>.

Description

Testing Instructions

Risk Assessment [HIGH || MEDIUM || LOW]

• I, the PR creator, have tested — integration, unit, or otherwise — this code.

Reviewer Checklist (To be checked off by the reviewer only)

• JIRA Ticket is referenced in PR title.
• Correctness & Style
  • Conforms to AOSP Style Guides
  • Mission critical pieces are documented in code and out of code as needed.
• Unit Tests reviewed and test issue sufficiently.
• Functionality was reviewed in QA independently by another engineer on the team.

cc @BranchMetrics/saas-sdk-devs for visibility.

[matter-code-review]

Reference

SDK-XXX -- Release 6.0.0-alpha.1.

Description

Summary By MatterAI

🔄 What Changed

This pull request updates the project's version from 5.20.3 to 6.0.0-alpha.1 and the corresponding VERSION_CODE from 052403 to 060000 in gradle.properties.

🔍 Impact of the Change

This change signifies a major version increment, moving from a stable release to an alpha release of version 6.0.0. It directly impacts the artifact version published and the Android application's internal version code, indicating a new development cycle or significant breaking changes from the previous major version. It aligns with standard versioning conventions for software releases.

📁 Total Files Changed

• gradle.properties: Updated VERSION_NAME and VERSION_CODE for the new release.

🧪 Test Added

N/A - This change is a configuration update and does not involve adding new code that requires unit or integration tests.

🔒Security Vulnerabilities

N/A - This change does not introduce or mitigate any security vulnerabilities as it only updates versioning properties.

Testing Instructions

N/A - This is a version bump in a configuration file. The primary 'testing' would involve a successful Gradle build and verification of the generated artifact's version.

Risk Assessment [LOW]

• I, the PR creator, have tested — integration, unit, or otherwise — this code.

Reviewer Checklist (To be checked off by the reviewer only)

• JIRA Ticket is referenced in PR title.
• Correctness & Style
  • Conforms to AOSP Style Guides
  • Mission critical pieces are documented in code and out of code as needed.
• Unit Tests reviewed and test issue sufficiently.
• Functionality was reviewed in QA independently by another engineer on the team.

cc @BranchMetrics/saas-sdk-devs for visibility.

Tanka Poem ♫

New version ascends,
Alpha dawn, a fresh start blooms.
Code evolves, expands,
Future features softly gleam,
Builds now sing a different tune. 🚀

Sequence Diagram

sequenceDiagram
    participant Developer
    participant GradleProperties as gradle.properties
    participant GradleBuildSystem as Gradle Build System
    participant PublishedArtifact as Published Artifact

    Developer->>GradleProperties: Update VERSION_NAME and VERSION_CODE
    Note over Developer,GradleProperties: Set to 6.0.0-alpha.1 and 060000
    GradleBuildSystem->>GradleProperties: Read version properties
    GradleBuildSystem->>GradleBuildSystem: Configure build with new versions
    GradleBuildSystem-->>PublishedArtifact: Generate/Publish artifact (v6.0.0-alpha.1)

Loading

[matter-code-review]

Important

PR Review Skipped

PR review skipped as per the configuration setting. Run a manually review by commenting /matter review

💡Tips to use MatterAI

Command List

• /matter summary: Generate AI Summary for the PR
• /matter review: Generate AI Reviews for the latest commit in the PR
• /matter review-full: Generate AI Reviews for the complete PR
• /matter release-notes: Generate AI release-notes for the PR
• /matter : Chat with your PR with MatterAI Agent
• /matter remember : Generate AI memories for the PR
• /matter explain: Get an explanation of the PR
• /matter help: Show the list of available commands and documentation
• Need help? Join our Discord server: https://discord.gg/fJU5DvanU3

[bboothe-branch]

Should we mention the showShareSheet() function's update? Or is that not relevant here?