[Arghya Dutta (silabs-ArghyaD)]

Issue Link: MATTER-6602

Description of Problem/Feature:
Phase 2 of Package Manager Implementation. Enabled Scripts and CI workflows.
Confluence Page - Matter Extension Github Repository and Build Process Package Manager

Description of Fix/Solution:

• Add the slcp changes.
• Add changes and suggestions from the reviews of the Phase 1 PR.
  -- Modify version update script to update matter_package_version
  -- Remove uploading sqa artifacts to UBAI
  -- Move installing conan to cache tools action
  -- Set CONAN_HOME as global and not in each step
• Enable CIs to package manager implementation.
• Kept the existing CIs, but removed the triggers (can be triggered manually).
• Updated package naming logic for PRs and branch runs.
• Add package promotion stage in Jenkins.
• Remove SQA Smoke and Regression trigger stages from Jenkins.

Testing Done:

• Will be tested in this PR CI.

[cursor]

PR Summary

High Risk
Touches release Jenkins (Conan publish/promote, UBAI target versioning) and retargets PR CI to package-based builds—failures block merges and can mis-version artifacts.

Overview
Phase 2 wires Matter Conan/SLT package builds into the main CI path and Jenkins release flow, while legacy submodule-based dev-app workflows are demoted to manual dispatch.

GitHub Actions centralizes CONAN_HOME, Conan on PATH, and slt install conan in cache-tools / install-tools, and drops per-step Conan bootstrapping in package create/restore actions. The use-package-cache flag is removed—*-pkg workflows always build from cached matter / matter_app packages. Matter Packages Validation becomes the PR gate on main / release_* (export packages, then nested dev-app and OTA checks); daily cron triggers that workflow instead of standalone dev-apps builds. Package builder artifact collection now stages only artifact/ outputs and .map files under preserved out/ paths. Non-package builder.yaml rewrites WiFi sdk_extension wifi → wiseconnect3_sdk at build time for the wifi submodule. SQA app builds use a workflow-start weekday rule (America/New_York Thursday on release branches).

Jenkins resolves MATTER_PACKAGE_VERSION before artifact upload, tags UBAI metadata with that version, enables Create and Publish Matter Packages via action-conan-create-publish (v2.5.4), and adds Promote Matter Packages to SQA on release branches. SQA smoke/regression pipeline triggers and separate SQA artifact upload stages are removed.

Packages / SLC: WiFi example SLCPs reference the wifi extension id; dependency_versions.yaml and LwIP component provides align with package naming; matter_package_version is the Conan version source of truth (updated by update_version.py); Conan packaging adds experimental quality and extra BLE/CMP sources.

^{Reviewed by Cursor Bugbot for commit 6b3dde3. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 6b3dde3. Configure here.}

[Michael Duggan (miduggan24)]

the old jenkins jobs are pending on this PR as they are set at repo level as required checks
https://github.com/SiliconLabsDevOps/github-config/blob/main/organization-config/SiliconLabsSoftware/repos/matter_extension/matter_extension.tf#L5-L9

need to update this. can't remove repo-wide yet of course, but may be some way to require for all branches outside of 2.10.

[sarthak shaha (Sarthak-Shaha)]

Left a first pass comments.

[Arghya Dutta (silabs-ArghyaD)]

Apologies, this had already been cleaned up following your previous comments, but it came back from a test branch where I was testing the CI wiring.

You’re right: with CONAN_HOME in GITHUB_ENV from cache-tools / install-tools, we don’t need a separate conan-home input/output. I’ve trimmed it again; cache save/restore now uses ${{ env.CONAN_HOME }}.

[Arghya Dutta (silabs-ArghyaD)]

Apologies, this had already been cleaned up following your previous comments, but it came back from a test branch where I was testing the CI wiring.

You’re right: with CONAN_HOME in GITHUB_ENV from cache-tools / install-tools, we don’t need a separate conan-home input/output. I’ve trimmed it again; cache save/restore now uses ${{ env.CONAN_HOME }}.

This is the updated flow -

[sarthak shaha (Sarthak-Shaha)]

Please resolve all comments, looks good.