Prep for v1.11.1

[odow]

Pre-release

• Check that the pinned packages in docs/Project.toml are updated. We pin
  the versions so that changes in the solvers (changes in printing, small
  numeric changes) do not break the printing of the JuMP docs in arbitrary
  commits.
• Check that the rev fields in docs/packages.toml are updated. We pin
  the versions of solvers and extensions to ensure that changes to their
  READMEs do not break the JuMP docs in arbitrary commits, and to ensure
  that the versions are compatible with the latest JuMP and
  MathOptInterface releases.
• Update docs/src/changelog.md
• Run https://github.com/jump-dev/JuMP.jl/actions/workflows/extension-tests.yml
  using a workflow_dispatch trigger to check for any changes in JuMP that
  broke extensions.
  * https://github.com/jump-dev/JuMP.jl/actions/runs/4942011171
• Change the version number in Project.toml
• Update the links in README.md
• The commit messages in this PR do not contain [ci skip]
  (See Documenter#965.)

The release

• After merging this pull request, comment @JuliaRegistrator register in
  the GitHub commit. This should automatically publish a new version to the
  Julia registry, as well as create a tag, and rebuild the documentation
  for this tag.

  These steps can take quite a bit of time (1 hour or more), so don't be
  surprised if the new documentation takes a while to appear. In addition,
  the links in the README will be broken until JuliaHub fetches the new
  version on their servers.
  

Post-release

• Once the tag is created, update the relevant release- branch. The latest
  release branch at the time of writing is release-1.0 (we haven't
  back-ported any patches that needed to create a release-1.Y branch). To
  to update the release branch with the v1.10.0 tag, do:
  git checkout release-1.0 git pull git merge v1.10.0 git push

[JuliaRegistrator]

Comments on pull requests will not trigger Registrator, as it is disabled. Please try commenting on a commit or issue.

[odow]

cc @pulsipher do you have time to look at InfiniteOpt with the latest master?

I'm seeing lots of errors: https://github.com/jump-dev/JuMP.jl/actions/runs/4942011171/jobs/8835171512

I don't know what would have caused the issue on our end.

[codecov]

Codecov Report

Patch and project coverage have no change.

Comparison is base (dd66846) 98.06% compared to head (1078495) 98.06%.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #3350   +/-   ##
=======================================
  Coverage   98.06%   98.06%           
=======================================
  Files          34       34           
  Lines        4919     4919           
=======================================
  Hits         4824     4824           
  Misses         95       95           

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[pulsipher]

Hmmm, I'll take a closer look tonight or early tomorrow (EST).

[odow]

It seems this is actually a Julia v1.9 issue. I'll keep digging

[odow]

InfiniteOpt confirmed as unrelated to JuMP. Some weird bug on Julia v1.9...

[odow]

@blegat happy?