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.12.0 #3417

Merged
merged 7 commits into from
Jun 19, 2023
Merged

Prep for v1.12.0 #3417

merged 7 commits into from
Jun 19, 2023

Conversation

odow
Copy link
Member

@odow odow commented Jun 9, 2023

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/5217354658
  • 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 @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
Copy link

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

@codecov
Copy link

codecov bot commented Jun 9, 2023

Codecov Report

Patch coverage has no change and project coverage change: -0.08 ⚠️

Comparison is base (269742f) 98.05% compared to head (3db0067) 97.97%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #3417      +/-   ##
==========================================
- Coverage   98.05%   97.97%   -0.08%     
==========================================
  Files          34       34              
  Lines        4924     4928       +4     
==========================================
  Hits         4828     4828              
- Misses         96      100       +4     

see 5 files with indirect coverage changes

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

@odow odow requested a review from blegat June 9, 2023 22:56
@odow
Copy link
Member Author

odow commented Jun 19, 2023

Bump @blegat. Lot's of stuff here.

@odow odow merged commit c5935e6 into master Jun 19, 2023
@odow odow deleted the od/v1.12.0 branch June 19, 2023 19:25
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