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.19.0 #3663

Merged
merged 1 commit into from
Feb 1, 2024
Merged

Prep for v1.19.0 #3663

merged 1 commit into from
Feb 1, 2024

Conversation

odow
Copy link
Member

@odow odow commented Jan 31, 2024

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
  • https://github.com/jump-dev/JuMP.jl/actions/runs/7733391585
  • Change the version number in Project.toml
  • Update the links in README.md
  • 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 Jan 31, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (42cd6c1) 98.29% compared to head (6445aac) 98.29%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #3663   +/-   ##
=======================================
  Coverage   98.29%   98.29%           
=======================================
  Files          43       43           
  Lines        5676     5676           
=======================================
  Hits         5579     5579           
  Misses         97       97           

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

@blegat
Copy link
Member

blegat commented Feb 1, 2024

@hdavid16 @pulsipher The tests of DisjunctiveProgramming.jl are failing, is that because of the new JuMP version ?
See https://github.com/jump-dev/JuMP.jl/actions/runs/7733391585 for the failure

@pulsipher
Copy link
Contributor

@hdavid16 @pulsipher The tests of DisjunctiveProgramming.jl are failing, is that because of the new JuMP version ? See https://github.com/jump-dev/JuMP.jl/actions/runs/7733391585 for the failure

This is simply due to a printing change (a bug fix) that occurred with JuMP 1.18. I have a PR that fixes this hdavid16/DisjunctiveProgramming.jl#110. Feel free to release 1.19.

@odow odow merged commit e4d2d7f into master Feb 1, 2024
12 checks passed
@odow odow deleted the od/v1.19.0 branch February 1, 2024 23:06
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.

3 participants