Is there a new version to release?

[isaacsanders]

My team had some issues with a different library that made the switch in their rebar config from plugins to project_plugins, and I was hoping there was a new release of the library that we could use to take advantage of the change made about 2 years ago in #283.

[nixxquality]

The fun_parent error is hitting me, which wouldn't be an issue with a new version, since I see you already patched it.

[zmstone]

Another reason to cut a release rather sooner than later is the slave module deprecation.

[evnu]

@kostis a new release of PropEr would be appreciated for alfert/propcheck#226 (comment) as well. Can we help with making a release happen?

[michalwski]

What's preventing the new PropEr release?

[lsigauke]

@kostis could we please create a new release for PropEr? I desperately need https://github.com/alfert/propcheck to release their updated version which removes the use of a deprecated function call.

[kostis]

Hi to all. For a while now, I spend most of my time on other projects, and the time I can spend on PropEr is quite limited. But this week is, surprisingly, considerably less busy. I can create a new release (1.5.0) if there is some feedback that what currently exists on the master branch of PropEr works OK and does not have any (new) issues. Can somebody confirm this?

[evnu]

@kostis One datapoint: I ran the testsuite of propcheck against 5640d07, which completed successfully.

diff --git a/mix.exs b/mix.exs
index 6d14140..3b4fac6 100644
--- a/mix.exs
+++ b/mix.exs
@@ -90,9 +90,9 @@ defmodule PropCheck.Mixfile do
     [
       # This is the reference to proper on its github repo - instable.
       # {:proper, "~> 1.3", github: "proper-testing/proper"},
-      {:proper, "~> 1.4"},
+      {:proper, git: "https://github.com/proper-testing/proper.git"},
       {:libgraph, "~> 0.13"},
-      {:coverex, "~> 1.4", only: :test},
+      # {:coverex, "~> 1.4", only: :test},
       {:credo, "~> 1.4", only: [:dev, :test], runtime: false},
       {:dialyxir, "~> 1.0.0", only: [:dev, :test], runtime: false},
       {:ex_doc, "~> 0.21", only: :dev}
diff --git a/mix.lock b/mix.lock
index 1f5d24d..7af466e 100644
--- a/mix.lock
+++ b/mix.lock
@@ -19,7 +19,7 @@
   "nimble_parsec": {:hex, :nimble_parsec, "1.1.0", "3a6fca1550363552e54c216debb6a9e95bd8d32348938e13de5eda962c0d7f89", [:mix], [], "hexpm", "08eb32d66b706e913ff748f11694b17981c0b04a33ef470e33e11b3d3ac8f54b"},
   "parse_trans": {:hex, :parse_trans, "3.3.0", "09765507a3c7590a784615cfd421d101aec25098d50b89d7aa1d66646bc571c1", [:rebar3], [], "hexpm", "17ef63abde837ad30680ea7f857dd9e7ced9476cdd7b0394432af4bfc241b960"},
   "poison": {:hex, :poison, "3.1.0", "d9eb636610e096f86f25d9a46f35a9facac35609a7591b3be3326e99a0484665", [:mix], [], "hexpm", "fec8660eb7733ee4117b85f55799fd3833eb769a6df71ccf8903e8dc5447cfce"},
-  "proper": {:hex, :proper, "1.4.0", "89a44b8c39d28bb9b4be8e4d715d534905b325470f2e0ec5e004d12484a79434", [:rebar3], [], "hexpm", "18285842185bd33efbda97d134a5cb5a0884384db36119fee0e3cfa488568cbb"},
+  "proper": {:git, "https://github.com/proper-testing/proper.git", "5640d0715d4b346676267504d8e84398e2a29f75", []},
   "ssl_verify_fun": {:hex, :ssl_verify_fun, "1.1.5", "6eaf7ad16cb568bb01753dbbd7a95ff8b91c7979482b95f38443fe2c8852a79b", [:make, :mix, :rebar3], [], "hexpm", "13104d7897e38ed7f044c4de953a6c28597d1c952075eb2e328bc6d6f2bfc496"},
   "unicode_util_compat": {:hex, :unicode_util_compat, "0.4.1", "d869e4c68901dd9531385bb0c8c40444ebf624e60b6962d95952775cac5e90cd", [:rebar3], [], "hexpm", "1d1848c40487cdb0b30e8ed975e34e025860c02e419cb615d255849f3427439d"},
 }

[apexsloth]

Run on our in-house test suite for different Elixir applications using PropCheck.
No issues:

22 doctests, 24 properties, 173 tests, 0 failures
1 doctest, 21 properties, 19 tests, 0 failures, 8 excluded
115 doctests, 44 properties, 113 tests, 0 failures
1 doctest, 7 properties, 73 tests, 0 failures
34 doctests, 85 properties, 340 tests, 0 failures, 6 excluded
11 properties, 63 tests, 0 failures

diff --git a/mix.exs b/mix.exs
index 78c5bb32f3..8141f81d0a 100644
--- a/mix.exs
+++ b/mix.exs
+      {:proper, git: "https://github.com/proper-testing/proper.git", override: true},
diff --git a/mix.lock b/mix.lock
index a2083c6c3b..c7f5ccbe45 100644
--- a/mix.lock
+++ b/mix.lock
@@ -101 +101 @@
-  "proper": {:hex, :proper, "1.4.0", "89a44b8c39d28bb9b4be8e4d715d534905b325470f2e0ec5e004d12484a79434", [:rebar3], [], "hexpm", "18285842185bd33efbda97d134a5cb5a0884384db36119fee0e3cfa488568cbb"},
+  "proper": {:git, "https://github.com/proper-testing/proper.git", "5640d0715d4b346676267504d8e84398e2a29f75", []},

[kostis]

Thanks @evnu and @linges for your help here. Given a base case (@evnu's datapoint) and an inductive hypothesis (@linges' datapoint), I've applied engineer's induction and operated under the assumption that the current master works everywhere!

There is a new release. Enjoy!

Now, if some kind soul (@ferd ?) can upload this also to Hex.pm (because I do not have write access there), I would appreciate it -- and then I can close this issue.

[alfert]

@kostis thank you for your effort! Now let's create a new propcheck release after Hex.pm is updated

[ferd]

I was at a conference all of last week, I'll try to tackle publication this week.

[kostis]

I was at a conference all of last week, I'll try to tackle publication this week.

Great (for the conference last week -- I hope it was interesting / inspiring) and great for the plans this week !

[ferd]

So PropEr was already at version 1.4.0 in Hex. We need to bump the version in this repository. Looking at the changeset since tag v1.4, going to 1.4.1 in src/proper.app.src would probably be adequate. Then I can push a new version.

Sent a PR at #322

(Conference was pretty interesting, thanks!)

[ferd]

1.5.0 is out on Hex https://hex.pm/packages/proper/1.5.0