@@ -3,6 +3,10 @@
         "version": "latest",
         "url": "https://nvidia.github.io/cuda-python/cuda-core/latest/"
     },
+    {
+        "version": "1.3.0",
+        "url": "https://nvidia.github.io/cuda-python/cuda-core/1.3.0/"
+    },
     {
         "version": "1.2.2",
         "url": "https://nvidia.github.io/cuda-python/cuda-core/1.2.2/"
 
@@ -11,6 +11,18 @@ Highlights
 
 - Support for Python 3.10 is dropped (end of life).
 
+- ``cuda.core`` now requires a minimum ``cuda-bindings`` version per CUDA major: 12.9.8 for
+  CUDA 12 and 13.5.0 for CUDA 13. See the breaking changes below.
+
+- :class:`VirtualMemoryResource` buffers can be shared with other processes through POSIX file
+  descriptors or fabric handles.
+
+- :func:`host_launch` enqueues a Python callable or a compiled host function on a stream in
+  stream order.
+
+- A new :doc:`error handling <../error_handling>` policy: :class:`CUDAWarning` reports CUDA
+  errors that cannot be raised, and :class:`CUDAOutOfMemoryError` is a :class:`MemoryError`.
+
 Breaking Changes
 ----------------
 
@@ -72,8 +84,27 @@ New features
   linker. :meth:`Linker.link` also accepts ``"ltoir"`` on nvJitLink 13.3 or
   newer so incremental LTO chains can retain IR until their final link. Direct
   PTX and CUBIN inputs are rejected for this target because they carry no LTOIR
-  and nvJitLink would otherwise silently omit them.
-  (`#2369 <https://github.com/NVIDIA/cuda-python/issues/2369>`__)
+  and nvJitLink would otherwise silently omit them. Incremental links with
+  link-time optimization disable the nvJitLink intermediate cache, which
+  crashed after repeated links on Windows.
+  (`#2369 <https://github.com/NVIDIA/cuda-python/issues/2369>`__,
+  `#3038 <https://github.com/NVIDIA/cuda-python/issues/3038>`__)
+
+- Added the ``priority`` option to :class:`LaunchConfig`, which sets the
+  execution priority of a kernel launch. Lower numbers are higher priorities.
+  The valid range is the device's stream priority range, as for
+  :attr:`StreamOptions.priority`. A nonzero value outside it raises
+  ``ValueError``.
+  (`#2631 <https://github.com/NVIDIA/cuda-python/issues/2631>`__)
+
+- Added the ``cluster_scheduling_policy_preference`` option to
+  :class:`LaunchConfig`: ``"DEFAULT"``, ``"SPREAD"``, or
+  ``"LOAD_BALANCING"``. It requires compute capability 9.0 or newer.
+  (`#2629 <https://github.com/NVIDIA/cuda-python/issues/2629>`__)
+
+- The PyTorch tensor bridge uses the stable ``PyObject`` to ``Tensor`` C API
+  of PyTorch 2.14 and newer, and no longer caps the supported PyTorch
+  version. PyTorch 2.3 to 2.13 keep the previous path.
 
 - Added the read-only :attr:`ManagedBuffer.last_prefetch_location` property,
   which reports the destination requested by the most recent explicit
@@ -296,8 +327,8 @@ Fixes and enhancements
 
 - When a :class:`Device` method has to run in the device's context and the
   caller's context cannot be restored afterwards, the created resource is
-  destroyed and the raised ``CUDAError`` now carries a note (Python 3.11+;
-  appended to the message on 3.10) stating that the caller's context could not
+  destroyed and the raised ``CUDAError`` now carries a note
+  stating that the caller's context could not
   be restored and which context is current. Previously the error named only
   the driver status of the failed ``cuCtxSetCurrent`` call. If the call itself
   failed as well, its error is raised and the restoration failure is the note.
@@ -315,8 +346,7 @@ Fixes and enhancements
   context is current, returning ``None``.
 
 - A failed rollback of a partially embedded child graph node is now attached
-  as a note to the exception that triggered the rollback (reported as
-  :class:`CUDAWarning` on Python 3.10), and a failed ``cuStreamEndCapture``
+  as a note to the exception that triggered the rollback, and a failed ``cuStreamEndCapture``
   made when a still-building :class:`~graph.GraphBuilder` is garbage collected
   is now reported as :class:`CUDAWarning`; both were silent.
 
@@ -447,6 +477,33 @@ Fixes and enhancements
   cuda.core error, please report".
   (`#3202 <https://github.com/NVIDIA/cuda-python/issues/3202>`__)
 
+- A process that made a device current with :meth:`Device.set_current` no
+  longer crashes at interpreter shutdown. The primary context was released
+  from a thread-local destructor after Python had finalized.
+  (`#2743 <https://github.com/NVIDIA/cuda-python/issues/2743>`__)
+
+- :meth:`Buffer.from_ipc_descriptor` no longer deadlocks when two threads
+  import IPC buffers at the same time.
+  (`#2840 <https://github.com/NVIDIA/cuda-python/issues/2840>`__)
+
+- :class:`Linker` passes boolean nvJitLink options as ``1`` or ``0``.
+  Newer nvJitLink versions reject the ``true`` and ``false`` values that it
+  passed before.
+  (`#3254 <https://github.com/NVIDIA/cuda-python/issues/3254>`__)
+
+- :class:`Program` with ``code_type="nvvm"`` now raises :class:`CUDAError`
+  for twelve :class:`ProgramOptions` fields that libNVVM cannot use, such as
+  ``pch`` and ``no_cache``. Before, they were silently ignored.
+  (`#2954 <https://github.com/NVIDIA/cuda-python/issues/2954>`__)
+
+- A failed IPC export that receives an invalid file descriptor from the
+  driver now raises the original error. The rollback used to close the
+  invalid descriptor and replace the error with ``EBADF``.
+
+- A new graph no longer adopts the metadata of a destroyed graph when the
+  driver reuses its handle address. Cleanup of the old graph could
+  invalidate the new one.
+
 Deprecations
 ------------
 
@@ -456,3 +513,15 @@ Deprecations
 
   - ``TimeoutError`` is now ``NvmlTimeoutError``.
   - ``MemoryError`` is now ``NvmlMemoryError``.
+
+Known issues
+------------
+
+- :class:`PinnedMemoryResource` rejects ``HOST_NUMA`` pools on CUDA 12.6 to
+  12.8 drivers, although the driver supports them. This regression is present
+  since 1.2.0.
+  (`#2795 <https://github.com/NVIDIA/cuda-python/issues/2795>`__)
+
+- :meth:`SMResource.split` with ``dry_run=True`` raises on
+  CUDA 13 when a group requests a nonzero SM count.
+  (`#2765 <https://github.com/NVIDIA/cuda-python/issues/2765>`__)
@@ -32,7 +32,7 @@
         f"cuda-bindings{matcher}{version}",
         # Bump this with every cuda-core release and release cuda-python right
         # after it; see .github/RELEASE-core.md and cuda_python/AGENTS.md.
-        "cuda-core~=1.2.0",
+        "cuda-core~=1.3.0",
         "cuda-pathfinder~=1.1",
     ],
     extras_require={