#############
Release Notes
#############


License Key
===========

HOOPS Exchange only requires a new license key if you are currently using a key which was generated for a prior *major version*.
For example, developers upgrading from 2025.1.0 to 2025.2.0 may use the same key, but those upgrading from 2025.1.0 to 2026.1.0 need to generate a new key.
Please visit the `HOOPS Exchange download page <https://developer.techsoft3d.com/hoops/exchange/downloads/latest/>`_ if you need to generate a new key.
The key is delivered in the file *include/hoops_license.h*. Once you have generated a new key, you should copy the file to *<EXCHANGE_INSTALL_DIR>/include/*.

The expiration date for the generated license key is tied to your contract with Tech Soft 3D. If you have signed a license agreement for HOOPS Exchange,
then the license key that is generated will be a perpetual (non-expiring) license key.
If you are evaluating HOOPS Exchange, then the license key will expire when your evaluation expires.
**Evaluation license keys will expire at the end of the evaluation period and are not suitable for production software.
Any software that uses an evaluation license key will no longer work after the evaluation period.**

HOOPS Exchange releases are not binary compatible with older releases.
**You must recompile your application when updating to a new version of HOOPS Exchange.**
Please see :doc:`/distributing` section for an up-to-date list of binaries required for distribution.

.. note:: 

   Visit our `Developer Support page <https://developer.techsoft3d.com/developer-support/>`_ to familiarize yourself with support procedures, including deprecated functionality.

_______________________________________________________________________________

.. toctree::
   :titlesonly:
   :maxdepth: 2
   :glob:
   :reversed:

   /fixed_bugs
   release_notes/v*
   release_notes/20*  

.. note::

   For release notes related to HOOPS Publish, see the legacy :doc:`release notes index </release_notes/hp-then/release_notes>`.
