Skip to content

Conversation

odow
Copy link
Member

@odow odow commented Oct 6, 2025

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.
  • Check compat of DimensionalData in Project.toml
  • Check compat of MacroTools in Project.toml
  • Update docs/src/changelog.md
  • https://github.com/jump-dev/JuMP.jl/actions/runs/18269419696
  • Change the version number in Project.toml
  • The commit messages in this PR do not contain [ci skip]

The release

  • After merging this pull request, comment [at]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

Copy link

codecov bot commented Oct 6, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.86%. Comparing base (7d1f0d8) to head (2755066).

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #4081   +/-   ##
=======================================
  Coverage   99.86%   99.86%           
=======================================
  Files          43       43           
  Lines        5910     5910           
=======================================
  Hits         5902     5902           
  Misses          8        8           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@odow
Copy link
Member Author

odow commented Oct 6, 2025

@joaquimg are these known failures with BilevelJuMP? I don't think I've made any changes here that are the problem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant