the-moby-effect 1.43.0-alpha.1 → 1.43.0-alpha.2

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.
Files changed (2) hide show
  1. package/README.md +7 -7
  2. package/package.json +6 -6
package/README.md CHANGED
@@ -2,7 +2,7 @@
2
2
 
3
3
  Moby API client built using [effect-ts](http://effect.website). If you want documentation, please consider reading [The Docker API documentation](https://docs.docker.com/engine/api/latest), it is very well written and there is nothing in this library that wouldn't be in there (plus I would just do a worse job if I tried to write my interpretation of their documentation here). If you are just looking for some examples to get your feet underneath you quickly with effect integration, then I do have some of those [here](./examples/).
4
4
 
5
- ## Goals
5
+ ## Goals :white_check_mark:
6
6
 
7
7
  - [x] - local unix socket connections
8
8
  - [x] - http and https connections
@@ -13,18 +13,18 @@ Moby API client built using [effect-ts](http://effect.website). If you want docu
13
13
  - [x] - Strong focus on types and typescript support
14
14
  - [x] - Support multiple "engines" (docker, podman, ect). If its built on top of [moby](https://github.com/moby/moby) then it _should_ just work, however, __currently only docker is tested against__
15
15
 
16
- ## Non-Goals
16
+ ## Non-Goals :wastebasket:
17
17
 
18
18
  - Tighter schema: the moby api schema is pretty loose as it aims to be backwards compatible - almost nothing is explicitly marked as required and object properties are optional by default under the swagger2.0/openapi specification. I have no intention to try to tighten their schema in my project. If the moby schema doesn't explicitly mark it as a required field, then it will be optional.
19
19
 
20
20
  - Version negotiating: either install a specific version for the moby api that you are targeting or just keep your docker install somewhat up-to-date and you should have no problems
21
21
 
22
- ## Todo/Future
22
+ ## Todo/Future :bulb:
23
23
  - Add more examples
24
24
  - Maybe add tests against something else other than docker like podman?
25
25
  - Patch upstream @effect/platform-node to support just streaming responses, needed for session and container attach endpoints: [upstream pr](https://github.com/Effect-TS/effect/pull/1796)
26
26
 
27
- ## Compatibility
27
+ ## Compatibility :closed_lock_with_key:
28
28
 
29
29
  the-moby-effect targets the current stable version of the moby api, which is v1.43 at the time of writing. If you are curious what that translates to for docker versions then take a look at [this](https://docs.docker.com/engine/api/#api-version-matrix) api version matrix published by Docker. As stated in the api version matrix, only Docker v24.0 would be officially supported by the-moby-effect, however, we still test against docker v20, v23, v24, and the next release candidate which is v25 (there is no v21 or v22 btw). Here is another note from Docker:
30
30
 
@@ -34,10 +34,10 @@ the-moby-effect targets the current stable version of the moby api, which is v1.
34
34
 
35
35
  The only compatibility issue found so far is that when using the-moby-effect with docker v20 you can not filter or prune volumes using the `all` filter as it was not present at the time. Other than that all functionality appears to still work.
36
36
 
37
- ## Versioning
37
+ ## Versioning :rotating_light:
38
38
 
39
39
  This package does not follow semantic versioning, instead the major and minor part represents the version of the moby api. All bugfixes, breaking or otherwise, will be released under an incremented patch version.
40
40
 
41
- ## Contributing and getting help
41
+ ## Contributing and getting help :speech_balloon: :beers:
42
42
 
43
- Contributions, suggestions, and questions are welcome! I'll review prs and respond to issues/discussion here on GitHub but if you want more direct and probably quicker communication you can find me in the [effect discord](https://discord.gg/effect-ts) as @leonitous
43
+ Contributions, suggestions, and questions are welcome! I'll review prs and respond to issues/discussion here on GitHub but if you want more synchronous communication you can find me in the [effect discord](https://discord.gg/effect-ts) as @leonitous
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "the-moby-effect",
3
- "version": "1.43.0-alpha.1",
3
+ "version": "1.43.0-alpha.2",
4
4
  "description": "Docker daemon API client built using effect-ts",
5
5
  "keywords": [
6
6
  "moby",
@@ -22,7 +22,7 @@
22
22
  "ssh2": "^1.15.0"
23
23
  },
24
24
  "devDependencies": {
25
- "@effect/experimental": "0.5.2",
25
+ "@effect/experimental": "0.5.3",
26
26
  "@effect/platform": "0.39.0",
27
27
  "@effect/platform-node": "0.39.0",
28
28
  "@effect/schema": "0.56.1",
@@ -43,19 +43,19 @@
43
43
  "fast-check": "3.15.0",
44
44
  "prettier": "3.1.1",
45
45
  "prettier-plugin-jsdoc": "1.3.0",
46
- "prettier-plugin-packagejson": "2.4.7",
46
+ "prettier-plugin-packagejson": "2.4.8",
47
47
  "tar-fs": "3.0.4",
48
48
  "tsx": "^4.7.0",
49
49
  "typescript": "5.3.3",
50
- "ws": "8.15.1"
50
+ "ws": "8.16.0"
51
51
  },
52
52
  "peerDependencies": {
53
- "@effect/experimental": "0.5.2",
53
+ "@effect/experimental": "0.5.3",
54
54
  "@effect/platform-node": "~0.39.0",
55
55
  "@effect/schema": "~0.56.1",
56
56
  "effect": "~2.0.0-next.62",
57
57
  "fast-check": "~3.15.0",
58
- "ws": "~8.15.1"
58
+ "ws": "~8.16.0"
59
59
  },
60
60
  "engines": {
61
61
  "node": ">=16"