Pre-release 0.10.1rc1

[ymzayek]

No description provided.

[github-actions]

👋 @ymzayek Thanks for creating a PR!

Until this PR is ready for review, you can include the [WIP] tag in its title, or leave it as a github draft.

Please make sure it is compliant with our contributing guidelines. In particular, be sure it checks the boxes listed below.

• PR has an interpretable title.
• PR links to Github issue with mention Closes #XXXX (see our documentation on PR structure)
• Code is PEP8-compliant (see our documentation on coding style)
• Changelog or what's new entry in doc/changes/latest.rst (see our documentation on PR structure)

For new features:

• There is at least one unit test per new function / class (see our documentation on testing)
• The new feature is demoed in at least one relevant example.

For bug fixes:

• There is at least one test that would fail under the original bug conditions.

We will review it as quick as possible, feel free to ping us with questions if needed.

[codecov]

Codecov Report

Merging #3536 (733055a) into main (867d6f1) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #3536   +/-   ##
=======================================
  Coverage   90.99%   90.99%           
=======================================
  Files         133      133           
  Lines       15365    15365           
  Branches     3207     3207           
=======================================
  Hits        13982    13982           
  Misses        819      819           
  Partials      564      564           

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[bthirion]

When do you do the pre-release ?

[ymzayek]

I can do it today or tomorrow. We should hold off on merging anything else at this point until I do the release and a post-release PR. Once the tests pass I'd say it's ready.

[Remi-Gau]

Good with me but let me know if I should make a mention of the changes in terms of formatting.

I am starting to feel that it may be better to keep track regularly of those changes rather than having a single entry "in the end" because the end may take a while to get there and some changes involve more than just "reformatting" so it may help to have some bread crumbs for those in the changelog.

[ymzayek]

@Remi-Gau we could go ahead and add it in this PR. Maybe an entry (or more if needed) under changes? I think it's worth mentioning the reformatting since this could concern contributors in general, however I think I would still leave CI stuff out. I was actually thinking to open an issue/PR to add to this README file to document everything that's happening with the CI (specifically GitHub Actions).

[bthirion]

LGTM

[ymzayek]

@Remi-Gau would it suffice to add this?

- Modules :mod:`~nilearn.decomposition` and :mod:`~nilearn.decoding` code and docstrings have been reformatted using black. Changes resulted in improved readability overall and increased consistency (:gh:`3491` and :gh:`3484` by `Remi Gau`_).

[Remi-Gau]

@Remi-Gau would it suffice to add this?

- Modules :mod:`~nilearn.decomposition` and :mod:`~nilearn.decoding` code and docstrings have been reformatted using black. Changes resulted in improved readability overall and increased consistency (:gh:`3491` and :gh:`3484` by `Remi Gau`_).

Yes that's good with me. Thanks.

[ymzayek]

Merging this. Then will tag it, build, and upload the distributions to pypi and github