RATATOSK
← All releases

hamiv2.7.0

Security 3Breaking changes 14Important fixes 14Enhancements 15Dependency updates 9Other changes 37

Get hami alerts

Email is sent weekly only when there are changes to check; critical security advisories are sent immediately.

Security3

HAMi scheduler Helm RBAC now uses scoped roles

AffectsHAMi Helm chart installations using the hami-scheduler service account and its generated RBAC bindings

Previously, the chart gave hami-scheduler the broad cluster-admin role. The chart now grants explicit permissions for HAMi's required resources and namespace-level lease operations, and binds the scheduler to the built-in system:kube-scheduler and system:volume-scheduler roles.

Show release-note lines
* feat(scheduler-role): use a scoped-down role for scheduler by @Antvirf in https://github.com/Project-HAMi/HAMi/pull/1152
github.com/Project-HAMi/HAMi/releases/tag/v2.7.0

HAMi image package updates for Trivy-reported issues

AffectsDeployments using the HAMi image built from this Dockerfile(Inferred)

Before this release, Trivy reported security issues in the image, but the PR does not identify them individually. The build now runs dnf update -y on the nvidia/cuda:12.6.3-base-ubi8 stage while excluding cuda-toolkit-config-common and cuda-toolkit-12-config-common; the PR says this helps resolve the findings, not that each is confirmed fixed.

Show release-note lines
* fix: deal with security issues reported by Trivy in image by @Shouren in https://github.com/Project-HAMi/HAMi/pull/1189
github.com/Project-HAMi/HAMi/releases/tag/v2.7.0

Go build configuration security fix

AffectsHAMi deployments built from its image or source(Inferred)

The build image and go.mod previously used Go 1.24.4. The PR does not identify the affected code path or runtime conditions.

Show release-note lines
* fix(security): resolve issues reported by Code scanning in Security by @Shouren in https://github.com/Project-HAMi/HAMi/pull/1280
github.com/Project-HAMi/HAMi/releases/tag/v2.7.0

Breaking changes14

vGPU allocation metrics gain new metrics and deprecation labels

Affectsmonitoring and automation consuming HAMi's vGPU allocation metrics(Inferred)
Removed inv2.8.0

Monitoring now receives vGPUMemoryAllocated and vGPUCoreAllocated; the existing vGPUPodsDeviceAllocated, vGPUMemoryPercentage, and vGPUCorePercentage metrics continue with a deprecated_version="v2.8.0" label and help text announcing their planned deprecation.

Evidence“This pr removes and replaces it with two metrics that already exist.” Project-HAMi/HAMi/pull/1169 ↗
Show release-note lines
* remove redundant metrics for vgpu allocation by @FouoF in https://github.com/Project-HAMi/HAMi/pull/1169
github.com/Project-HAMi/HAMi/releases/tag/v2.7.0

HAMi now defaults GPU core limits to 100

AffectsNVIDIA GPU workloads requesting the GPU-count resource with exclusive memory and no explicit GPU-core resource in requests or limits

Previously, HAMi left GPU cores unset in this case, with nvidia.defaultCores remaining 0 by default. Newly admitted matching pods receive a core-resource limit of 100, and GPUDeviceCoreAllocated and vGPUCoreAllocated reflect 100; existing pod specs change only when recreated or reapplied, while explicit core values and non-exclusive-memory cases remain unchanged.

Evidence“The GPU core resource (config.ResourceCoreName, default nvidia.com/gpucores) must be absent from both limits and requests; explicit values are never overwritten.” Project-HAMi/HAMi/pull/1354 ↗
Show release-note lines
* feat(nvidia): default gpucores=100 when memory is exclusive and cores… by @xrwang8 in https://github.com/Project-HAMi/HAMi/pull/1354
github.com/Project-HAMi/HAMi/releases/tag/v2.7.0

HAMi webhook can replace Kubernetes's default scheduler name

AffectsHAMi webhook-admitted pods with Pod.Spec.SchedulerName set to DefaultSchedulerName, and installations configuring scheduler settings through the chart or flag

The behavior is controlled by the chart setting forceOverwriteDefaultScheduler or the scheduler flag --force-overwrite-default-scheduler; both default to true.

Evidence“+ rootCmd.Flags().BoolVar(&config.ForceOverwriteDefaultScheduler, "force-overwrite-default-scheduler", true, "Overwrite schedulerName in Pod Spec when set to the const DefaultSchedulerName in https://k8s.io/api/core/v1 package")” Project-HAMi/HAMi/pull/1163 ↗
Show release-note lines
* fix: Add option for overwrite schedulerName by @Shouren in https://github.com/Project-HAMi/HAMi/pull/1163
github.com/Project-HAMi/HAMi/releases/tag/v2.7.0

GPU device numeric conversions now use checked casts

Affectsnode annotations with device counts, memory, or core values; NVIDIA MIG health events; and device CPU affinity(Inferred)

Direct casts could produce incorrect converted values, and node-annotation numeric fields were cast to int32 without a range check. Now, an unrepresentable annotation value returns a decode error, an unconvertible CPU-affinity value returns nil, and unconvertible or nonmatching MIG health-event IDs are skipped.

Evidence“affinity, err := safecast.ToUint(node)” Project-HAMi/HAMi/pull/1183 ↗
Show release-note lines
* fix: using go-safecast to fix incorrect conversion of numbers by @Shouren in https://github.com/Project-HAMi/HAMi/pull/1183
github.com/Project-HAMi/HAMi/releases/tag/v2.7.0

Metax sGPU QoS policy selection via Pod annotation

AffectsMetax sGPU jobs

Previously, Metax sGPU admission neither defaulted an omitted policy nor validated a supplied one. Now, omitted annotations assign best-effort; best-effort, fixed-share, and burst-share are accepted, while other values are rejected at admission.

Evidence“Support Metax sGPU Qos Policy: user can specify qos policy for job” Project-HAMi/HAMi/pull/1123 ↗
Show release-note lines
* Support Metax sGPU Qos Policy by @Kyrie336 in https://github.com/Project-HAMi/HAMi/pull/1123
github.com/Project-HAMi/HAMi/releases/tag/v2.7.0

Metax sGPU fitting rejects unhealthy devices

AffectsMetax sGPU device scheduling(Inferred)

A device with Health=false fails the fit check and cannot be selected for the request.

Show release-note lines
* Support Metax sGPU device health check by @Kyrie336 in https://github.com/Project-HAMi/HAMi/pull/1295
github.com/Project-HAMi/HAMi/releases/tag/v2.7.0

Helm chart version and default image tag updated to 2.7.0

AffectsHelm chart installations using the default image tag, and systems that read chart version metadata(Inferred)

The chart’s appVersion changes from 2.6.1 to 2.7.0.

Show release-note lines
* update chart version and hami-core by @archlitchi in https://github.com/Project-HAMi/HAMi/pull/1369
github.com/Project-HAMi/HAMi/releases/tag/v2.7.0

NVIDIA device scheduling now honors ResourceQuota limits

AffectsNVIDIA device requests in namespaces with applicable ResourceQuota limits(Inferred)

Applicable device-resource limits are used during scheduling. The scheduler also exposes QuotaUsed metrics labeled with the quota namespace, name, and limit.

Evidence“This pr add resource quota support for Nvidia multi-device request and whole device request.” Project-HAMi/HAMi/pull/1359 ↗
Show release-note lines
* NVIDIA Resourcequota by @FouoF in https://github.com/Project-HAMi/HAMi/pull/1359
github.com/Project-HAMi/HAMi/releases/tag/v2.7.0

String processing now uses strings.SplitSeq

AffectsNVIDIA, Enflame, Hygon, or Kunlun device support and utility string processing(Inferred)

These loops previously created a slice with strings.Split before iterating over its elements. They now range over strings.SplitSeq instead, which the change describes as more efficient.

Evidence“The `SplitSeq` method is introduced in strings package since Go 1.24.0, and ranging over `SplitSeq` is more efficient” Project-HAMi/HAMi/pull/1239 ↗
Show release-note lines
* refactor: Ranging over SplitSeq is more efficient by @Shouren in https://github.com/Project-HAMi/HAMi/pull/1239
github.com/Project-HAMi/HAMi/releases/tag/v2.7.0

vGPUmonitor switches to an informer-backed local pod cache

Affectssetups running vGPUmonitor

Previously, vGPUmonitor frequently queried the API server to check whether pods existed and reconcile container information; it now updates a local cache from informer events and reconciles periodically. Container-list refresh is 30 seconds by default, while informer resync is five minutes and configurable with HAMI_RESYNC_INTERVAL.

Evidence“This PR adds an informer-based pod cache mechanism to the vGPUmonitor component to significantly reduce Kubernetes API server load.” Project-HAMi/HAMi/pull/1250 ↗
Show release-note lines
* feat: add informer-based pod cache to reduce API server load by @miaobyte in https://github.com/Project-HAMi/HAMi/pull/1250
github.com/Project-HAMi/HAMi/releases/tag/v2.7.0

Devices.Fit annotation parameter removed

AffectsGo integrations that implement or call HAMi's device.Devices interface, including custom device implementations(Inferred)

Previously, annotation-dependent checks used an annotation map passed separately from the pod. They now use annotations from the supplied pod.

Evidence“- Fit(devices []*DeviceUsage, request ContainerDeviceRequest, annos map[string]string, pod *corev1.Pod, nodeInfo *NodeInfo, allocated *PodDevices) (bool, map[string]ContainerDevices, string) + Fit(devices []*DeviceUsage, request ContainerDeviceRequest, pod *corev1.Pod, nodeInfo *NodeInfo, allocated *PodDevices) (bool, map[string]ContainerDevices, string)” Project-HAMi/HAMi/pull/1343 ↗
Show release-note lines
* refactor: Remove annotation in Devices interfaces by @Shouren in https://github.com/Project-HAMi/HAMi/pull/1343
github.com/Project-HAMi/HAMi/releases/tag/v2.7.0

Helm chart image values moved to nested per-image objects

AffectsHelm chart image overrides using the old scalar fields or separate image settings(Inferred)

Previously, image names were scalar values, with settings such as pull policy and tag in separate fields; those settings now belong in per-image objects.

Show release-note lines
* add global image for chart by @calvin0327 in https://github.com/Project-HAMi/HAMi/pull/1133
github.com/Project-HAMi/HAMi/releases/tag/v2.7.0

Node locking switches to Patch as the chart removes Node update permission

AffectsHAMi deployments using pkg/util/nodelock and the chart-managed scheduler role

Previously, node locking used Update on Nodes, and the chart granted the scheduler get, list, patch, update, and watch on Nodes.

Evidence“- verbs: ["get", "list", "patch", "update", "watch"] + verbs: ["get", "list", "patch", "watch"]” Project-HAMi/HAMi/pull/1192 ↗
Show release-note lines
* perf(util/nodelock): Use clientset Patch instead of Update. by @mayooot in https://github.com/Project-HAMi/HAMi/pull/1192
github.com/Project-HAMi/HAMi/releases/tag/v2.7.0

Ascend 910A and 910B3 resource names corrected

AffectsAscend 910A or 910B3 device configurations and resource names(Inferred)

The 910B entry previously used huawei.com/Ascend910B; it now uses huawei.com/Ascend910B3, and the 910A and 910B3 devices are identified separately. Existing configurations must use the corrected names.

Evidence“This pr changed device resource name, so the user must update their configs.” Project-HAMi/HAMi/pull/1315 ↗
Show release-note lines
* cleanup: Clear and correct ascend device name by @FouoF in https://github.com/Project-HAMi/HAMi/pull/1315
github.com/Project-HAMi/HAMi/releases/tag/v2.7.0

Important fixes14

  • Kunlun node scores revised and device overrides added to defaults
    Affectsnode scoring for Kunlun devices and registered device types(Inferred)

    When scoring nodes with Kunlun devices, some cases returned lower values (for example, 2000 for a difference of -1) based on the change between current and previous countbubble values. For registered device types, an override replaced the default score only when positive; scores now add the device-specific override to the default.

    * fix: override node socre failure for kunlun #1137 by @ouyangluwei163 in https://github.com/Project-HAMi/HAMi/pull/1138
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.0
  • Multi-node scheduler override scoring accuracy fixed
    Affectsmulti-node scheduling with user node-policy override scoring(Inferred)

    Override scoring now uses a captured device-usage snapshot for each node's scoring calculation.

    * fix: Multi-node scoring nodes are inaccurate by @ouyangluwei163 in https://github.com/Project-HAMi/HAMi/pull/1147
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.0
  • Admission webhook logs now use Pod identity
    AffectsHAMi admission webhook logs(Inferred)

    When logging admission requests, req.UID could differ from the Pod UID, and req.Name could be empty on CREATE if the client omitted the name. Logs now use the Pod's namespace, name, and UID, including in denial, admission, and error-related entries.

    * fix: wrong Pod's UID and emtpy Pod's name in log of webhook.go by @Shouren in https://github.com/Project-HAMi/HAMi/pull/1092
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.0
  • Incorrect NVIDIA NUMA node results fixed
    AffectsNVIDIA GPU topology parsing with HAMi's NVIDIA device plugin(Inferred)

    When parsing NVIDIA NUMA topology, the parser could return the wrong NUMA node; the multi-GPU test expects index 4 to resolve to 1.

    * fix: fix err which retrieved incorrect NUMA node information issue #1275 by @abstractmj in https://github.com/Project-HAMi/HAMi/pull/1276
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.0
  • Admission webhook preserves explicit Pod scheduler choices
    AffectsPods with a nonempty spec.schedulerName that differs from HAMi's configured scheduler, or with no configured scheduler name

    Previously, the webhook could override an explicitly assigned scheduler while continuing to process the Pod. It now admits matching Pods without further webhook handling.

    * fix: Skip admission webhook when Pod's scheduler is already assigned. by @ghostloda in https://github.com/Project-HAMi/HAMi/pull/1041
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.0
  • Ascend 910B4-1 device support added
    AffectsSetups using Ascend 910B4-1 devices(Inferred)

    The chart configuration includes the device’s resource identifiers and the vir05_1c_8g and vir10_3c_16g templates.

    * FIx CI, add 910B4-1 template and fix vGPUmonitor metrics error by @archlitchi in https://github.com/Project-HAMi/HAMi/pull/1345
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.0
  • NVIDIA vGPUmonitor metric calculations corrected
    Affectssetups using NVIDIA vGPUmonitor metrics(Inferred)

    Previously, the calculations iterated over every slot in s.sr.procs, rather than only the first procnum slots. They now use only the process slots counted by procnum.

    * FIx CI, add 910B4-1 template and fix vGPUmonitor metrics error by @archlitchi in https://github.com/Project-HAMi/HAMi/pull/1345
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.0
  • NVIDIA MIG mode-switch startup error fixed
    AffectsNVIDIA device-plugin setups with devices supported by configured MIG templates

    When operatingmode changed from mig to hami-core and nvidia-mig-parted did not turn off MIG, hami-core ran with an error. The non-mig startup path now creates and applies a MIG-disabled configuration for supported devices.

    * featue: mig mode-change #1116 by @ouyangluwei163 in https://github.com/Project-HAMi/HAMi/pull/1124
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.0
  • Iluvatar device fitting now processes devices in forward order
    AffectsIluvatar device scheduling and allocation(Inferred)

    Creating an Iluvatar pod could error when fitting traversed the device list in reverse.

    * fix: An error occurred while create Iluvatar pod by @ouyangluwei163 in https://github.com/Project-HAMi/HAMi/pull/1149
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.0
  • Concurrent map-access panic in scheduler scoring fixed
    AffectsConcurrent node scoring by the HAMi scheduler(Inferred)

    When one goroutine wrote to a map while another read or wrote it during calcScore, concurrent map access could panic. The fitting-node and failed-node result writes now use separate mutexes, preventing that panic in this code path.

    * fix: concurrent map writes error in scheduler.calcScore #1269 by @Shouren in https://github.com/Project-HAMi/HAMi/pull/1270
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.0
  • HAMi NodeLock cleanup for Bind errors and dangling locks
    AffectsHAMi scheduler NodeLock for Pod binding and device allocation

    If the owner Pod was deleted after the scheduler set its NodeLock but before device allocation finished, subsequent Pods needing the same node could remain pending until the lock expired; a PatchPodAnnotations error during Bind also left the lock uncleared. This release clears the lock on that Bind error and allows dangling locks to be removed before expiry, including by non-holder Pods under timeout or dangling conditions.

    * fix: release dangling node lock by @peachest in https://github.com/Project-HAMi/HAMi/pull/1271
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.0
  • Scheduler device allocation now includes containers without device requests
    AffectsMulti-container pods with device requests(Inferred)

    Previously, allocation omitted a container with no device request when a later container requested a device. In the tested two-container case, the allocation now includes an empty entry for the first container and the device allocation for the second.

    * Fix: device allocation missing containers with no device request by @FouoF in https://github.com/Project-HAMi/HAMi/pull/1299
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.0
  • NVIDIA MIG allocation now matches equal-memory templates
    AffectsNVIDIA MIG device scheduling

    Before this fix, a request whose memory exactly matched a MIG template could fail to match a device and return CardNotFoundCustomFilterRule.

    * If the mem applied for the Mig device is the same as the template value,>will result in CardNotFoundCustom Filter Rule. by @zgqqiang in https://github.com/Project-HAMi/HAMi/pull/1179
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.0
  • Unhealthy NVIDIA GPU scheduling flaw fixed
    AffectsPod scheduling that requests NVIDIA GPUs

    When a Pod requested an NVIDIA GPU with health=false, the scheduler still admitted it, but the Pod did not run. The fit check now rejects unhealthy GPUs before binding and logs card details at verbosity 5.

    * bugfix: Nvidia card abnormal pod will still continue to schedule by @zgqqiang in https://github.com/Project-HAMi/HAMi/pull/1336
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.0

Enhancements15

  • Topology-aware scheduling for 100%-core Metax sGPU allocations

    To use Enable metaxsGPUTopologyAware or set metax-tech.com/sgpu-topology-aware to true.

    * Metax sGPU topology aware by @Kyrie336 in https://github.com/Project-HAMi/HAMi/pull/1193
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.0
  • Kunlunxin scheduling supports four-card requests across NUMA boundaries
    * Kunlunxin topology-aware scheduling by @FouoF in https://github.com/Project-HAMi/HAMi/pull/1141
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.0
  • Kunlunxin vXPU resource support
    * Kunlunxin vxpu sopport #1016 by @ouyangluwei163 @archlitchi  in https://github.com/Project-HAMi/HAMi/pull/1337
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.0
  • Whole-card scheduling for Enflame GCU S60

    To use gcu-k8s-device-plugin >= 2.0 on nodes

    * Enflame GCU topology-awareness  (#1040) by @zhaikangqi331 in https://github.com/Project-HAMi/HAMi/pull/1334
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.0
  • AWS Neuron device and device-core allocation added
    * AWS-neuron device and device-core allocation by @archlitchi in https://github.com/Project-HAMi/HAMi/pull/1238
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.0
  • Aggregated scheduling-failure details in Pod events
    * Aggregated Scheduling Failure Events by @Wangmin362 in https://github.com/Project-HAMi/HAMi/pull/1333
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.0
  • Configurable HAMi scheduler node-lock timeout

    To use Optional --node-lock-timeout flag; defaults to 5 minutes.

    * feat(scheduler): make node lock timeout configurable by @Kevinz857 in https://github.com/Project-HAMi/HAMi/pull/1117
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.0
  • Optional disabling of the HAMi admission webhook

    To use Helm value scheduler.admissionWebhook.enabled set to false (defaults to true)

    * feat(helm): optionally disable admission webhook by @Antvirf in https://github.com/Project-HAMi/HAMi/pull/1145
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.0
  • Scheduler adds an unknown-node allocation log
    * refactor: clean up code and improve maintainability by @Wangmin362 in https://github.com/Project-HAMi/HAMi/pull/1195
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.0
  • HAMi node-lock timeout is configurable

    To use Set HAMI_NODELOCK_EXPIRE to a parseable duration, or set scheduler.nodeLockExpire in Helm.

    * feat:NodeLockTimeout set from env by @miaobyte in https://github.com/Project-HAMi/HAMi/pull/1244
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.0
  • Helm chart device-plugin resource toggle

    To use devicePlugin.enabled value, which defaults to true

    * feat: Add option to disable device plugin at values.yaml. by @FouoF in https://github.com/Project-HAMi/HAMi/pull/1274
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.0
  • Kunlun resource-name mapping added to the chart and device initialization
    * fix: override node socre failure for kunlun #1137 by @ouyangluwei163 in https://github.com/Project-HAMi/HAMi/pull/1138
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.0
  • Kunlunxin device support and topology-aware scheduling

    To use devices.kunlun.enabled: true and kunlunxin.com/xpu configured as a custom resource

    * Support topology-awareness for Kunlunxin device by @archlitchi in https://github.com/Project-HAMi/HAMi/pull/1121
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.0
  • Global Helm chart registry and image-pull-secret settings

    To use Configure global.imageRegistry and/or global.imagePullSecrets to use the corresponding setting.

    * add global image for chart by @calvin0327 in https://github.com/Project-HAMi/HAMi/pull/1133
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.0
  • Topology-aware scheduling for NVIDIA GPUs

    To use Set scheduler.defaultSchedulerPolicy.gpuSchedulerPolicy to topology-aware when installing HAMi; set ENABLE_TOPOLOGY_SCORE to true in the hami-device-plugin DaemonSet; add gpu-scheduler-policy=topology-aware when starting hami-scheduler; and set hami.io/gpu-scheduler-policy: topology-aware in Pod annotations.

    * feat: Add nvidia gpu topoloy scheduler by @fyp711 in https://github.com/Project-HAMi/HAMi/pull/1028
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.0

Dependency updates9

  • tensorflow/tensorflow upgraded from latest-gpu to 2.20.0rc0-gpu
    * [Snyk] Security upgrade tensorflow/tensorflow from latest-gpu to 2.20.0rc0-gpu by @wawa0210 in https://github.com/Project-HAMi/HAMi/pull/1243
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.0
8 more, none mentioning security
  • * fix: update int8Slice to uint8Slice for better type clarity and consistency by @yxxhero in https://github.com/Project-HAMi/HAMi/pull/1357
  • * fix: update int8Slice to uint8Slice for better type clarity and consistency by @yxxhero in https://github.com/Project-HAMi/HAMi/pull/1357
  • * fix: update int8Slice to uint8Slice for better type clarity and consistency by @yxxhero in https://github.com/Project-HAMi/HAMi/pull/1357
  • * fix: update int8Slice to uint8Slice for better type clarity and consistency by @yxxhero in https://github.com/Project-HAMi/HAMi/pull/1357
  • * build(deps): upgrade golang to 1.24.4 by @Shouren in https://github.com/Project-HAMi/HAMi/pull/1172
  • * build(deps): Upgrade controller-runtime to 0.21.0 by @Shouren in https://github.com/Project-HAMi/HAMi/pull/1171
  • * build(deps): Dump github.com/NVIDIA/nvidia-container-toolkit by @Shouren in https://github.com/Project-HAMi/HAMi/pull/1170
  • * [Misc] update hami-core version by @chaunceyjiang in https://github.com/Project-HAMi/HAMi/pull/1201
Other changes37

Summaries are produced by AI, so they can be wrong, and they are provided without warranty.