build(deps): update optuna requirement from <3.3.0,>=3.1.0 to >=3.1.0,<4.1.0

[dependabot[bot]]

Updates the requirements on optuna to permit the latest version.

Release notes

Sourced from optuna's releases.

v4.0.0

Here is the release note of v4.0.0. Please also check out the release blog post.

If you want to update the Optuna version of your existing projects to v4.0, please see the migration guide.

We have also published blog posts about the development items. Please check them out!

• OptunaHub, a Feature-Sharing Platform for Optuna, Now Available in Official Release!
• File Management during LLM (Large Language Model) Trainings by Optuna v4.0.0 Artifact Store
• Significant Speed Up of Multi-Objective TPESampler in Optuna v4.0.0

Highlights

Official Release of Feature-Sharing Platform OptunaHub

We officially released OptunaHub, a feature-sharing platform for Optuna. A large number of optimization and visualization algorithms are available in OptunaHub. Contributors can easily register their methods and deliver them to Optuna users around the world.

Please also read the OptunaHub release blog post.

Enhanced Experiment Management Feature: Official Support of Artifact Store

Artifact Store is a file management feature for files generated during optimization, dubbed artifacts. In Optuna v4.0, we stabilized the existing file upload API and further enhanced the usability of Artifact Store by adding some APIs such as the artifact download API. We also added features to show JSONL and CSV files on Optuna Dashboard in addition to the existing support for images, audio, and video. With this official support, the API backward compatibility will be guaranteed.

For more details, please check the blog post.

JournalStorage: Official Support of Distributed Optimization via Network File System

JournalStorage is a new Optuna storage experimentally introduced in Optuna v3.1 (see the blog post for details). Optuna has JournalFileBackend, a storage backend for various file systems. It can be used on NFS, allowing Optuna to scale to multiple nodes.

In Optuna v4.0, the API for JournalStorage has been reorganized, and JournalStorage is officially supported. This official support guarantees its backward compatibility from v4.0. For details on the API changes, please refer to the Optuna v4.0 Migration Guide.

import optuna
from optuna.storages import JournalStorage
from optuna.storages.journal import JournalFileBackend
def objective(trial: optuna.Trial) -> float:

...
storage = JournalStorage(JournalFileBackend("./optuna_journal_storage.log"))

study = optuna.create_study(storage=storage)

study.optimize(objective)

... (truncated)

Commits

• ef16a04 Merge pull request #5653 from eukaryo/bump-up-to-v4.0.0
• 5bb0af1 Update version.py
• e3eec34 Merge pull request #5649 from eukaryo/update-news-ingo-blog
• 0e6a6f0 Update README.md
• e63e336 Update README.md
• 7fd30c9 Merge pull request #5644 from kAIto47802/doc-add-install-visualization
• 3c15a3e Merge pull request #5648 from toshihikoyanase/remove-404-link
• 79201a7 Update tutorial/10_key_features/005_visualization.py
• 86ee356 Update README.md
• a10b917 Merge pull request #5637 from nabenabe0928/doc/add-sns-to-readme
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[fkiraly]

superseded by https://github.com/jdb78/pytorch-forecasting/pull/1629

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.