Skip to content

UD2025.48

Latest
Latest

Choose a tag to compare

View all tags
@Maxim-Doronin Maxim-Doronin released this 17 Dec 14:48
· 2 commits to develop since this release
Immutable release. Only release title and notes can be modified.
npu_ud_2025_48_rc1
This tag was signed with the committer’s verified signature.
Maxim-Doronin Maksim Doronin
SSH Key Fingerprint: 7+gbbQvTmv6AW0Mlh9QSW+IxrzJ3/6atSzxgWsgI8ro
Verified
Learn about vigilant mode.
a1ae54e
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Supported platforms

Release notes

The UD2025.48 Release Notes have been published as part of the Intel® NPU Windows Driver release notes, including the integrated NPU Compiler component.

Dependencies

NPU Linux Driver

The following driver version was used for NPU Compiler UD2025.48 Continuous Integration.

The following driver version contains NPU Compiler UD2025.48 as a binary component

Artifacts Information and supply-chain security

Click to expand

📦 Artifacts Information

This release provides three CiD (Compiler-in-Driver) binary packages for integration into the NPU Driver on the following platforms:

  • Windows 11
  • Ubuntu 22.04
  • Ubuntu 24.04

To ensure end-to-end supply-chain security, both the release and each individual artifact are protected by multiple integrity guarantees:

  • Digital signatures via Sigstore Cosign — any modification to a signed artifact invalidates the signature.
  • GitHub artifact provenance attestations — each artifact is accompanied by a build-provenance attestation published on the repository’s attestations page.
  • Immutable GitHub Release — the release tag and all assets are permanently locked after publication and cannot be modified, replaced, or deleted.

All commands below work on any platform. On Windows (CMD/PowerShell), simply replace the line-continuation symbol \ with ^.

🔐 Cosign Digital Signatures

Cosign provides cryptographic verification of both the artifact content and the associated Rekor entry. Together, these systems guarantee that each artifact originates exactly from this repository’s CI pipeline and has not been modified post-publication and allow anyone to validate that this artifact was produced by the official GitHub Actions workflow for this repository.
Each release artifact includes a signature bundle named:

<artifact>.sigstore.json

This bundle contains:

  • A Sigstore Fulcio certificate. Fulcio issues a short-lived signing certificate that binds the signature to the GitHub Actions workflow identity.
  • A Rekor transparency log entry. Rekor stores the transparency log record, ensuring the signature is publicly auditable and cannot be altered.
  • Signature metadata (SCT, inclusion proof, signature, etc.)

Verify the Signature Online

You can verify the published transparency-log record using:

https://search.sigstore.dev/?hash=<sha256>

To get the <sha256> digest, use the Copy SHA256 button next to any release asset in the GitHub release UI.

Verify the Signature Locally

  1. Install Cosign
    Follow the official guide: https://docs.sigstore.dev/cosign/system_config/installation
  2. Download the files
    • <artifact_name>
    • <artifact_name>.sigstore.json
  3. Run the verification 
    cosign verify-blob \
    --bundle <artifact_name>.sigstore.json \
    --certificate-identity https://github.com/openvinotoolkit/npu_compiler/.github/workflows/job_build_cid.yml@refs/tags/npu_ud_2025_48_rc1 \
    --certificate-oidc-issuer "https://token.actions.githubusercontent.com" \
    <artifact_name>
    Note: On Windows, the Cosign executable may be named differently (for example, cosign-windows-amd64.exe). Adjust the command accordingly when running verification.
  4. Successful verification 
    Verified OK

🧾 GitHub Release Asset Attestations (Build Provenance)

GitHub automatically generates a build-provenance attestation for each artifact created by GitHub Actions.

These attestations confirm:

  • Which workflow built the artifact
  • Which commit and tag were used
  • That the artifact content matches the workflow output exactly

Verify Attestation Locally

  1. Install & authenticate GitHub CLI
    Installation: https://cli.github.com/
    Login:

    gh auth login

  2. Verify the artifact attestation

    gh attestation verify <artifact_name> \
  --repo openvinotoolkit/npu_compiler \
  --source-ref refs/tags/npu_ud_2025_48_rc1 \
  --signer-workflow "github.com/openvinotoolkit/npu_compiler/.github/workflows/job_build_cid.yml@refs/tags/npu_ud_2025_48_rc1"

  3. Successful verification

    The following policy criteria will be enforced:
- Predicate type must match:................ https://slsa.dev/provenance/v1
- Source Repository Owner URI must match:... https://github.com/openvinotoolkit
- Source Repository URI must match:......... https://github.com/openvinotoolkit/npu_compiler
- Source repo ref must match:............... refs/tags/npu_ud_2025_48_rc1
- Subject Alternative Name must match regex: ^https://github.com/openvinotoolkit/npu_compiler/.github/workflows/job_build_cid.yml@refs/tags/npu_ud_2025_48_rc1
- OIDC Issuer must match:................... https://token.actions.githubusercontent.com

✓ Verification succeeded!

The following 1 attestation matched the policy criteria

- Attestation #1
  - Build repo:..... openvinotoolkit/npu_compiler
  - Build workflow:. .github/workflows/job_build_cid.yml@refs/tags/npu_ud_2025_48_rc1
  - Signer repo:.... openvinotoolkit/npu_compiler
  - Signer workflow: .github/workflows/job_build_cid.yml@refs/tags/npu_ud_2025_48_rc1

🛡️ Immutable GitHub Release Verification

Immutable Releases ensure that neither the release tag nor the associated assets can be changed after publication. This prevents supply-chain tampering and increases long-term auditability.

Verify the Integrity of the Release itself

  1. Install & authenticate GitHub CLI 
    gh auth login
  2. Verify the immutable release 
    gh release verify \
  --repo openvinotoolkit/npu_compiler \
  npu_ud_2025_48_rc1
  3. Successful verification
    GitHub CLI confirms that the release is immutable and the attestation is valid 
     Resolved tag npu_ud_2025_48_rc1 to sha1:216aab6488bb9be5893235d42d084945aded7f1f
 Loaded attestation from GitHub API
 ✓ Release npu_ud_2025_48_rc1 verified!
 
 Assets
 NAME                                                                                                                                                 DIGEST
 l_vpux_compiler_l0_linux_ubuntu_22_04-7_5_0-Release_dyntbb_postcommit_cid_a1ae54e94faea6f35566ef4ed03ee98156808306_251217_1334.tar.gz                sha256:e3bf9679f7b378dfcf00b936880182bf9d2db4998bc91d053b74f0594026a2d0
 l_vpux_compiler_l0_linux_ubuntu_22_04-7_5_0-Release_dyntbb_postcommit_cid_a1ae54e94faea6f35566ef4ed03ee98156808306_251217_1334.tar.gz.sigstore.json  sha256:249b4daf136cbbbb204df6daccdf6e1386274e916952f66987cc598e1e6cd06a
 l_vpux_compiler_l0_linux_ubuntu_24_04-7_5_0-Release_dyntbb_postcommit_cid_a1ae54e94faea6f35566ef4ed03ee98156808306_251217_1334.tar.gz                sha256:48de71e2121329e2e30216009a9fe2362f5543cb97e38f67878896baeb0138f7
 l_vpux_compiler_l0_linux_ubuntu_24_04-7_5_0-Release_dyntbb_postcommit_cid_a1ae54e94faea6f35566ef4ed03ee98156808306_251217_1334.tar.gz.sigstore.json  sha256:0f8dcdefb88e62f0cfae47594c457e3718a9a5859dbe4a7148518fc6d5d96844
 w_vpux_compiler_l0_win_windows_2022-7_5_0-Release_dyntbb_postcommit_cid_a1ae54e94faea6f35566ef4ed03ee98156808306_251217_1336.zip                     sha256:720a48f5bdc4ae2deeb9827ac3a37153776c57e9887817e6391e543579800641
 w_vpux_compiler_l0_win_windows_2022-7_5_0-Release_dyntbb_postcommit_cid_a1ae54e94faea6f35566ef4ed03ee98156808306_251217_1336.zip.sigstore.json       sha256:4b42013aacba2f78c13e8c567cd3228139ca3b2cc67203a20b8cc1c36e9496de
Assets 9
Loading