Skip to content

v1.4.0 Release #393

Description

@Radonirinaunimi

This issue collects what should go into the next v1.4.0, to decouple them from more fundamental changes such as #370 and #392 (?) which will eventually go into v1.5.0. These include fixes and documentations that have already been merged:

As well as still open issues on improving the documentations.

Activity

  1. linked a pull request that will close this issueFinalize Documentation #394on Mar 31, 2026
  2. cschwan commented on Apr 1, 2026

    @cschwan
    Contributor

    We should use Github's milestone features to mark thing we want to include.

  3. added this to the v1.4 milestone on Apr 1, 2026
  4. cschwan commented on Apr 2, 2026

    @cschwan
    Contributor

    One potential pitfall of the MSRV change is that RTD doesn't seem to support it yet. One potential solution could be to sneak in a --ignore-rust-version (some cargo applets support it), because the code actually doesn't use any features of Rust 1.92, 1.93 or 1.94 (yet).

  5. felixhekhorn commented on Apr 2, 2026

    @felixhekhorn
    Contributor

    since any change of supported version on RTD might be slow (is there any record on the speed?), it might be better to lower MSRV down to 1.91 instead

  6. Radonirinaunimi commented on May 11, 2026

    @Radonirinaunimi
    MemberAuthor

    Hi @cschwan, were there reasons you opened back the closed issues? I believe most of them have been addressed, no? For instance, #388 has been completed in 4e3f09c.

  7. cschwan commented on May 11, 2026

    @cschwan
    Contributor

    Dor some reason I thought that was a mistake, but go ahead and close them again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions