PackerBuildV0, PackerBuildV1 Node24 update

[Deekshitha2812]

Context

Node24 Update.
📌 AB#2350121

---

Task Name

PackerBuildV0
PackerBuildV1

---

Description

Updated the Tasks to support Node24. And the PackerBuildV1 is failing with errors Tests/L0.ts(60,16): error TS2339: Property 'run' does not exist on type 'MockTestRunner'. This is because of removal of run() function due to deasync in task-lib 4.12.1 version - Remove deasync . So changed run() into the runAsync() funtcion and make necessary changes.

---

Risk Assessment (Low / Medium / High)

Assess the level of risk and provide reasoning (e.g., scope, impact, backward compatibility).

---

Change Behind Feature Flag (Yes / No)

Can this change be behine feature flag, if not why?

---

Tech Design / Approach

• Design has been written and reviewed.
• Any architectural decisions, trade-offs, and alternatives are captured.

---

Documentation Changes Required (Yes/No)

Indicate whether related documentation needs to be updated.

• User guides, API specs, system diagrams, or runbooks are updated.

---

Unit Tests Added or Updated (Yes)

Unit Tests of PackerBuildV1 is updated.

---

Additional Testing Performed

List all other tests performed (manual or automated, including integration, regression, scenario tests, etc.).

---

Logging Added/Updated (Yes/No)

• Appropriate log statements are added with meaningful messages.
• Logging does not expose sensitive data.
• Log levels are used correctly (e.g., info, warn, error).

---

Telemetry Added/Updated (Yes/No)

• Custom telemetry (e.g., counters, timers, error tracking) is added as needed.
• Events are tagged with proper metadata for filtering and analysis.
• Telemetry is validated in staging or test environments.

---

Rollback Scenario and Process (Yes/No)

• Rollback plan is documented.

---

Dependency Impact Assessed and Regression Tested (Yes/No)

• All impacted internal modules, APIs, services, and third-party libraries are analyzed.
• Results are reviewed and confirmed to not break existing functionality.

---

Checklist

• Related issue linked (if applicable)
• Task version was bumped — see versioning guide
• Verified the task behaves as expected

[Deekshitha2812]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).