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

Prep for v1.21.0 #3718

Merged
merged 2 commits into from
Mar 31, 2024
Merged

Prep for v1.21.0 #3718

merged 2 commits into from
Mar 31, 2024

Conversation

odow
Copy link
Member

@odow odow commented Mar 27, 2024

TODO

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/8457321785
  • 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 Mar 27, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.42%. Comparing base (c3cefe0) to head (c9de5c3).
Report is 2 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #3718      +/-   ##
==========================================
+ Coverage   98.37%   98.42%   +0.04%     
==========================================
  Files          43       43              
  Lines        5737     5828      +91     
==========================================
+ Hits         5644     5736      +92     
+ Misses         93       92       -1     

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

@odow odow requested a review from blegat March 30, 2024 23:38
@odow
Copy link
Member Author

odow commented Mar 30, 2024

I don't plan to wait for #3685

@odow
Copy link
Member Author

odow commented Mar 31, 2024

Merging because we had talked about this on the developer call.

@odow odow merged commit 177d213 into master Mar 31, 2024
11 checks passed
@odow odow deleted the od/v1.21 branch March 31, 2024 21:13
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