concurrent-ruby-edge 0.7.0 → 0.7.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: f167a49a3185f5364fd2f6e4c3aa0b677e24027815a0b6680237b6b782de04a6
4
- data.tar.gz: e4b1aa280e5901d08e2d86d2c75c6a61a58d74eddc6f09800e454356f26b3ef2
3
+ metadata.gz: 86b56a758dd683a03bf65c0a78672be63dc0417956bb616572d54650ba964400
4
+ data.tar.gz: 8405da240566680bb1d032c085bfd6acb8fda6d277b00bfd234df2bd2ba70baa
5
5
  SHA512:
6
- metadata.gz: d68dba078cb11901127698aa8721c1f4bdb0f5688412ac7bf80b84408768b3687586937b92587b395435a725129b048aba763156282814b26e4e3e39eb2cae48
7
- data.tar.gz: 704ba13e3e7566beff49e9ef29f33eb1842a8e597e0d2054fec085eb7ff21839878064989894c002327d99ac29e42e38c797d8b118401fbcb40710e12c4040c9
6
+ metadata.gz: f9f71a67b03c3b2a0c3624f2fb2627cd810f6681e1790163934ad38df2315fe26f5a8b3fc698a92027529ac2ddf8ca3fee1164bbac7c6d7ae27fd6b6a7e7c6e1
7
+ data.tar.gz: ca53f6034c42805a9464274915b1ab56f1eb31addf91fd5a51244c006a9a2a43ed9d08ab0f811d239ec5cd8c5993da80f0faa16857209ab7541845cca48a93e2
data/CHANGELOG.md CHANGED
@@ -1,5 +1,33 @@
1
1
  ## Current
2
2
 
3
+ ## Edge 0.7.1 (7 June 2024)
4
+
5
+ concurrent-ruby-edge:
6
+
7
+ * (#1052) Fix dependency on `concurrent-ruby` to allow the latest release.
8
+
9
+ ## Release v1.3.1 (29 May 2024)
10
+
11
+ * Release 1.3.0 was broken when pushed to RubyGems. 1.3.1 is a packaging fix.
12
+
13
+ ## Release v1.3.0 (28 May 2024)
14
+
15
+ * (#1042) Align Java Executor Service behavior for `shuttingdown?`, `shutdown?`
16
+ * (#1038) Add `Concurrent.available_processor_count` that is cgroups aware.
17
+
18
+ ## Release v1.2.3 (16 Jan 2024)
19
+
20
+ * See [the GitHub release](https://github.com/ruby-concurrency/concurrent-ruby/releases/tag/v1.2.3) for details.
21
+
22
+ ## Release v1.2.2 (24 Feb 2023)
23
+
24
+ * (#993) Fix arguments passed to `Concurrent::Map`'s `default_proc`.
25
+
26
+ ## Release v1.2.1 (24 Feb 2023)
27
+
28
+ * (#990) Add missing `require 'fiber'` for `FiberLocalVar`.
29
+ * (#989) Optimize `Concurrent::Map#[]` on CRuby by letting the backing Hash handle the `default_proc`.
30
+
3
31
  ## Release v1.2.0 (23 Jan 2023)
4
32
 
5
33
  * (#962) Fix ReentrantReadWriteLock to use the same granularity for locals as for Mutex it uses.
data/README.md CHANGED
@@ -375,6 +375,8 @@ best practice is to depend on `concurrent-ruby` and let users to decide if they
375
375
  * [Benoit Daloze](https://github.com/eregon)
376
376
  * [Matthew Draper](https://github.com/matthewd)
377
377
  * [Rafael França](https://github.com/rafaelfranca)
378
+ * [Charles Oliver Nutter](https://github.com/headius)
379
+ * [Ben Sheldon](https://github.com/bensheldon)
378
380
  * [Samuel Williams](https://github.com/ioquatix)
379
381
 
380
382
  ### Special Thanks to
@@ -1,3 +1,3 @@
1
1
  module Concurrent
2
- EDGE_VERSION = '0.7.0'
2
+ EDGE_VERSION = '0.7.1'
3
3
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: concurrent-ruby-edge
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.7.0
4
+ version: 0.7.1
5
5
  platform: ruby
6
6
  authors:
7
7
  - Jerry D'Antonio
@@ -10,7 +10,7 @@ authors:
10
10
  autorequire:
11
11
  bindir: bin
12
12
  cert_chain: []
13
- date: 2023-01-23 00:00:00.000000000 Z
13
+ date: 2024-06-07 00:00:00.000000000 Z
14
14
  dependencies:
15
15
  - !ruby/object:Gem::Dependency
16
16
  name: concurrent-ruby
@@ -18,14 +18,14 @@ dependencies:
18
18
  requirements:
19
19
  - - "~>"
20
20
  - !ruby/object:Gem::Version
21
- version: 1.2.0
21
+ version: '1.3'
22
22
  type: :runtime
23
23
  prerelease: false
24
24
  version_requirements: !ruby/object:Gem::Requirement
25
25
  requirements:
26
26
  - - "~>"
27
27
  - !ruby/object:Gem::Version
28
- version: 1.2.0
28
+ version: '1.3'
29
29
  description: |
30
30
  These features are under active development and may change frequently. They are expected not to
31
31
  keep backward compatibility (there may also lack tests and documentation). Semantic versions will