Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: ruby/net-imap
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v0.6.1
Choose a base ref
...
head repository: ruby/net-imap
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v0.6.2
Choose a head ref
  • 4 commits
  • 4 files changed
  • 1 contributor

Commits on Dec 17, 2025

  1. 🐛 Fix SequenceSet#delete?(num..num) to return set 

    According to the rdoc, using a range with `#delete?` should return a
sequence set (or nil), but the check came after importing the input, and
was based on whether the imported run contained multiple values.  So
deleting a single number range (e.g: `1..1` or `"1:1"`) would return a
number not a set.
    @nevans
    nevans committed Dec 17, 2025
    Configuration menu
    Copy the full SHA
    d455729 View commit details
    Browse the repository at this point in the history

  2. 🔀 Merge tag 'v0.6.1' 

    Accidentally deployed 0.6.1 from a commit that hadn't been pushed to
master!
    @nevans
    nevans committed Dec 17, 2025
    Configuration menu
    Copy the full SHA
    dde67cf View commit details
    Browse the repository at this point in the history

  3. 🐛 Fix #responses() freezing internal arrays 

    Now that `:frozen_dup` is the default behavior for `#responses` when
it's called without any arguments, a critical bug has become apparent:
it was not freezing the internal responses arrays directly, rather than
copies of them.  Freezing these arrays will, of course, lead to further
issues.

Ideally, code should be updated to use one of the other forms of
`#responses`, since this form is less efficient and also (intentionally)
incompatibile with old code that expects it to return mutable arrays.
But this is still a major bug.

Fixes #581, reported by @yurikoval.
    @nevans
    nevans committed Dec 17, 2025
    Configuration menu
    Copy the full SHA
    96fd33b View commit details
    Browse the repository at this point in the history

  4. 🔖 Bump version to 0.6.2

    @nevans
    nevans committed Dec 17, 2025
    Configuration menu
    Copy the full SHA
    38622aa View commit details
    Browse the repository at this point in the history
Loading