Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: bad link in release #407

Merged
merged 1 commit into from
Mar 13, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/source/additional/release.rst
Original file line number Diff line number Diff line change
Expand Up @@ -66,7 +66,7 @@ Example of usage::
)


- Due to the two above features, many small breaking changes have been introduced, see the full [SubstraFL changelog](https://github.com/Substra/substrafl/blob/main/CHANGELOG.md) to get the comprehensive list of changes.
- Due to the two above features, many small breaking changes have been introduced, see the full `SubstraFL changelog <https://github.com/Substra/substrafl/blob/main/CHANGELOG.md>`_ to get the comprehensive list of changes.

Substra 0.35.0 --- 2024-02-26
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Expand Down Expand Up @@ -794,4 +794,4 @@ Substra
SubstraFL

- Throw an error if ``pytorch 1.12.0`` is used. There is a regression bug in ``torch 1.12.0``, that impacts optimizers that have been pickled and unpickled. This bug occurs for Adam optimizer for example (but not for SGD). Here is a link to one issue covering it: pytorch/pytorch#80345
- In the PyTorch algorithms, move the data to the device (GPU or CPU) in the training loop and predict function so that the user does not need to do it.
- In the PyTorch algorithms, move the data to the device (GPU or CPU) in the training loop and predict function so that the user does not need to do it.
Loading