In some places of our project we are using toMultimap() method which is marked as @Beta and consequently is considered as an unstable API.

See:
https://github.com/google/guava/blob/d7a26416109381a6770681bc6c299567615e8341/guava/src/com/google/common/collect/Multimaps.java#L108

So. There is already 29.0 version of Google Guava. When does it gonna be considered as a "stable API"?
I would provide you more examples of  similar "unstable API" methods from Guava...
@Override
    public boolean isEmpty() {
      return multimap.isEmpty();
    }
    @Override
    public boolean containsKey(Object key) {
      return multimap.containsKey(key);
    }
    @Override
    public void clear() {
      multimap.clear();
    }
  }
  /**
   * Returns a multimap containing the mappings in {@code unfiltered} whose keys satisfy a
   * predicate. The returned multimap is a live view of {@code unfiltered}; changes to one affect
   * the other.
   *
   * <p>The resulting multimap's views have iterators that don't support {@code remove()}, but all
   * other methods are supported by the multimap and its views. When adding a key that doesn't
   * satisfy the predicate, the multimap's {@code put()}, {@code putAll()}, and {@code
   * replaceValues()} methods throw an {@link IllegalArgumentException}.
   *
   * <p>When methods such as {@code removeAll()} and {@code clear()} are called on the filtered
   * multimap or its views, only mappings whose keys satisfy the filter will be removed from the
   * underlying multimap.
   *
   * <p>The returned multimap isn't threadsafe or serializable, even if {@code unfiltered} is.
   *
   * <p>Many of the filtered multimap's methods, such as {@code size()}, iterate across every