Adjust python-sample workflow runner matrix and diagnostics

[adilhusain-s]

Context

Python binaries used by GitHub Actions are produced and consumed across the following repositories:

• actions/python-versions builds and publishes Python release tarballs used by actions/setup-python
• IBM/python-versions-pz builds and publishes Python tarballs for ppc64le and s390x
• IBM/setup-python-pz consumes tarballs from IBM/python-versions-pz for ppc64le and s390x
• For amd64 and arm64, IBM/setup-python-pz redirects to the upstream actions/python-versions artifacts

This repository (python-versions-pz) provides the Python build artifacts consumed by IBM/setup-python-pz.

---

Purpose of the Sample Workflow

The python-sample.yml workflow is a reference example showing how an end user can consume Python using IBM/setup-python-pz across multiple architectures.

At present, IBM/setup-python-pz does not publish versioned tags. For that reason, the sample workflow intentionally uses:

uses: IBM/setup-python-pz@main

This reflects the current consumption model and avoids implying the existence of released tags.

---

Example Usage (for Consumers)

A minimal example of consuming Python using the IBM-provided setup action:

- name: Set up Python
  uses: IBM/setup-python-pz@main
  with:
    python-version: 3.14.2
    architecture: ppc64le

The sample workflow demonstrates this pattern across multiple runner architectures.

---

Summary

This PR updates the python-sample.yml workflow to make the runner matrix explicit and to add basic runtime visibility when consuming Python via IBM/setup-python-pz.

The change is limited to the sample workflow and does not affect build, release, or publishing logic.

---

Changes

• Rename the workflow for clarity

• Replace matrix.os with explicit runner and arch fields

• Use matrix.runner for runs-on

• Update the tested Python version from 3.13.4 to 3.14.2

• Add grouped log output showing:

  • Runner label
  • OS and kernel
  • Architecture
  • Python version and platform

• Rename the verification step to better reflect its purpose

---

Runner Matrix

The sample workflow runs on:

• ubuntu-24.04 (x64, GitHub-hosted)
• ubuntu-24.04-ppc64le (native hardware)
• ubuntu-24.04-s390x (native hardware)

---

Verification

The workflow was triggered manually and completed successfully on all matrix entries:

https://github.com/IBM/python-versions-pz/actions/runs/20787141292

---

Scope

• Sample workflow only
• No changes to Python build artifacts
• No changes to release or publishing logic

[mtarsel]

@adilhusain-s can we close this?