Skip to content

Commit

Permalink
Prep for v1.31.0 (#2521)
Browse files Browse the repository at this point in the history
  • Loading branch information
@odow
odow committed Jun 26, 2024
1 parent 5386a13 commit 1bee618
Show file tree
Hide file tree
Showing 2 changed files with 27 additions and 1 deletion.
2 changes: 1 addition & 1 deletion Project.toml
View file
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
name = "MathOptInterface"
uuid = "b8f27783-ece8-5eb3-8dc8-9495eed66fee"
version = "1.30.0"
version = "1.31.0"

[deps]
BenchmarkTools = "6e4b80f9-dd63-53aa-95a3-0cdb28fa8baf"
Expand Down
26 changes: 26 additions & 0 deletions docs/src/changelog.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,32 @@ CurrentModule = MathOptInterface
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## v1.31.0 (June 26, 2024)

### Added

- Added default `show(::IO, ::ModelLike)` method (#2505) (#2510)
- Set map bridges can now implement the various `map_function` methods to use
the value of the bridge as the first argument, instead of passing the type of
the bridge. (#2509)
- Added `cannot_unbridge` argument to [`Bridges.runtests`](@ref)

### Fixed

- Fixed [`supports_constraint`](@ref) for `IndicatorSOS1Bridge` (#2507)
- Fixed getting [`ConstraintDual`](@ref) in slack bridges (#2508) (#2514)
(#2515)
- Fixed `FileFormats.NL` to read linear constraints as
[`ScalarAffineFunction`](@ref) (#2512)
- Changed `default_copy_to` to maintain the order of variables during `copy_to`.
This change is marked as non-breaking, but it may cause different (but
mathematically equivalent) models to be formulated, particularly conic models
with bridges. (#2495) (#2520)

### Other

- Updated `solver-tests.yml` (#2516) (#2518)

## v1.30.0 (May 23, 2024)

### Added
Expand Down

2 comments on commit 1bee618

@odow
Copy link
Member Author

@odow odow commented on 1bee618 Jun 26, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JuliaRegistrator register

@JuliaRegistrator
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Registration pull request created: JuliaRegistries/General/109854

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v1.31.0 -m "<description of version>" 1bee6183f907ba63c585e032c57dd713124ff8b0
git push origin v1.31.0

Please sign in to comment.