Skip to content

Tags: jatinwadhwa921/onnxruntime

Tags

v5.5.1

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
ORT 1.20.0 release preparation: Cherry pick round 2 (microsoft#22643)

ORT 1.20.0 release preparation: Cherry pick round 2

Approved commits

---------

Co-authored-by: Hector Li <[email protected]>
Co-authored-by: ivberg <[email protected]>

v5.5

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
ORT 1.20.0 release preparation: Cherry pick round 2 (microsoft#22643)

ORT 1.20.0 release preparation: Cherry pick round 2

Approved commits

---------

Co-authored-by: Hector Li <[email protected]>
Co-authored-by: ivberg <[email protected]>

v5.4

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
ORT 1.19.0 Release: Cherry-Pick Round 2 (microsoft#21726)

### Description
<!-- Describe your changes. -->

PRs marked for cherry-pick & bug fixes.

### Motivation and Context
<!-- - Why is this change required? What problem does it solve?
- If it fixes an open issue, please link to the issue here. -->

ORT 1.19.0 Release Preparation

---------

Signed-off-by: Liqun Fu <[email protected]>
Co-authored-by: George Wu <[email protected]>
Co-authored-by: liqun Fu <[email protected]>
Co-authored-by: Scott McKay <[email protected]>
Co-authored-by: Yi Zhang <[email protected]>

v5.3.1

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Security Fuzz Test Fixes (microsoft#21608)

### Description
Fix address sanitizer and memory access Bug 1, 4, 5, 7, 8 found in
security fuzz test

### Motivation and Context
<!-- - Why is this change required? What problem does it solve?
- If it fixes an open issue, please link to the issue here. -->

v5.3

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
[ORT 1.18.0 Release] Cherry pick 3rd/Final round (microsoft#20677)

Co-authored-by: Rachel Guo <[email protected]>
Co-authored-by: rachguo <[email protected]>
Co-authored-by: rachguo <[email protected]>
Co-authored-by: Tianlei Wu <[email protected]>
Co-authored-by: George Wu <[email protected]>
Co-authored-by: Edward Chen <[email protected]>
Co-authored-by: Jian Chen <[email protected]>

OV5.2.x

LG Nuget Version

v5.2

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Update 1.17.1 patch release version (microsoft#19622)

### Description
<!-- Describe your changes. -->

Need to update patch release version.


### Motivation and Context
<!-- - Why is this change required? What problem does it solve?
- If it fixes an open issue, please link to the issue here. -->

---------

Co-authored-by: rachguo <[email protected]>
Co-authored-by: rachguo <[email protected]>

v5.1

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Update openvino_provider_factory.cc

Fix Lint issues

v5.0.1

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Merge pull request intel#319 from intel/customerA

Fix for when device_type is empty

v1.16.0

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Cherry-picks pipeline changes to 1.16.0 release branch (microsoft#17577)

### Description
1. Delete Prefast tasks (microsoft#17522)
2. Disable yum update (microsoft#17551)
3. Avoid calling patchelf (microsoft#17365 and microsoft#17562) we that we can validate
the above fix

The main problem I'm trying to solve is: our GPU package depends on both
CUDA 11.x and CUDA 12.x . However, it's not easy to see the information
because ldd doesn't work with the shared libraries we generate(see issue
microsoft#9754) . So the patchelf change are useful for me to validate the
"Disabling yum update" was successful. As you can see we call "yum
update" from multiple places. Without some kind of validation it's hard
to say if I have covered all of them.
The Prefast change is needed because I'm going to update the VM images
in the next a few weeks. In case of we need to publish a patch release
after that.

### Motivation and Context
Without this fix we will mix using CUDA 11.x and CUDA 12.x. And it will
crash every time when we use TensorRT.