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.18.0 #3636

Merged
merged 8 commits into from
Jan 2, 2024
Merged

Prep for v1.18.0 #3636

merged 8 commits into from
Jan 2, 2024

Conversation

odow
Copy link
Member

@odow odow commented Dec 19, 2023

TODOs

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/7281139642
  • 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 Dec 19, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (232a95d) 98.28% compared to head (787752a) 98.28%.
Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #3636   +/-   ##
=======================================
  Coverage   98.28%   98.28%           
=======================================
  Files          43       43           
  Lines        5640     5640           
=======================================
  Hits         5543     5543           
  Misses         97       97           

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

@odow
Copy link
Member Author

odow commented Dec 20, 2023

#3639 is high-priority bug-fix, so I'd move that we merge this without waiting for a resolution on #3635

docs/src/changelog.md Outdated Show resolved Hide resolved
docs/src/changelog.md Outdated Show resolved Hide resolved
@odow odow requested review from blegat and mlubin December 28, 2023 20:13
docs/src/changelog.md Outdated Show resolved Hide resolved
@odow odow merged commit 66184ef into master Jan 2, 2024
12 checks passed
@odow odow deleted the od/v1.18.0 branch January 2, 2024 04:47
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.

2 participants