@btravstack/storage 0.19.0 → 0.20.0

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 (7) hide show
  1. package/dist/index.d.cts +1 -1
  2. package/dist/index.d.mts +1 -1
  3. package/dist/s3.d.cts +1 -1
  4. package/dist/s3.d.mts +1 -1
  5. package/dist/{storage-Cu27C7Oq.d.cts → storage-BLJtJ7KF.d.cts} +4 -3
  6. package/dist/{storage-Cu27C7Oq.d.mts → storage-BLJtJ7KF.d.mts} +4 -3
  7. package/package.json +8 -8
package/dist/index.d.cts CHANGED
@@ -1,4 +1,4 @@
1
- import { a as StorageService, i as StorageBackend, n as PresignNotSupported, o as StorageUnavailable, r as Storage, s as StoredObject, t as ObjectNotFound } from "./storage-Cu27C7Oq.cjs";
1
+ import { a as StorageService, i as StorageBackend, n as PresignNotSupported, o as StorageUnavailable, r as Storage, s as StoredObject, t as ObjectNotFound } from "./storage-BLJtJ7KF.cjs";
2
2
  import { Module, Provider } from "@btravstack/di";
3
3
  import { HealthChecks } from "@btravstack/core";
4
4
  //#region src/memory.d.ts
package/dist/index.d.mts CHANGED
@@ -1,4 +1,4 @@
1
- import { a as StorageService, i as StorageBackend, n as PresignNotSupported, o as StorageUnavailable, r as Storage, s as StoredObject, t as ObjectNotFound } from "./storage-Cu27C7Oq.mjs";
1
+ import { a as StorageService, i as StorageBackend, n as PresignNotSupported, o as StorageUnavailable, r as Storage, s as StoredObject, t as ObjectNotFound } from "./storage-BLJtJ7KF.mjs";
2
2
  import { Module, Provider } from "@btravstack/di";
3
3
  import { HealthChecks } from "@btravstack/core";
4
4
  //#region src/memory.d.ts
package/dist/s3.d.cts CHANGED
@@ -1,4 +1,4 @@
1
- import { a as StorageService, i as StorageBackend } from "./storage-Cu27C7Oq.cjs";
1
+ import { a as StorageService, i as StorageBackend } from "./storage-BLJtJ7KF.cjs";
2
2
  import { Module, Scope } from "@btravstack/di";
3
3
  import { S3Client } from "@aws-sdk/client-s3";
4
4
  import { ConfigInvalid, Env } from "@btravstack/config";
package/dist/s3.d.mts CHANGED
@@ -1,4 +1,4 @@
1
- import { a as StorageService, i as StorageBackend } from "./storage-Cu27C7Oq.mjs";
1
+ import { a as StorageService, i as StorageBackend } from "./storage-BLJtJ7KF.mjs";
2
2
  import { Module, Scope } from "@btravstack/di";
3
3
  import { S3Client } from "@aws-sdk/client-s3";
4
4
  import { ConfigInvalid, Env } from "@btravstack/config";
package/dist/{storage-Cu27C7Oq.d.cts → storage-BLJtJ7KF.d.cts} RENAMED
@@ -47,9 +47,10 @@ type StorageService = {
47
47
  *
48
48
  * **`contentType` and `contentLength` are signed, not advisory.** They are
49
49
  * part of the signature, so a client sending different ones is refused by the
50
- * store: the URL grants exactly one write, of exactly that many bytes, of
51
- * exactly that type. `contentLength` is therefore required — an unsigned
52
- * length would hand out an unbounded write, and there is no ceiling a
50
+ * store. The same URL can write the key repeatedly until expiry, replacing
51
+ * the previous object with different bytes of that size and type. Neither
52
+ * signed header proves the bytes. `contentLength` is required — an unsigned
53
+ * length would allow an unbounded single write, and there is no ceiling a
53
54
  * presigned PUT can express other than the exact number.
54
55
  *
55
56
  * The application still decides every input: whether this caller may write
package/dist/{storage-Cu27C7Oq.d.mts → storage-BLJtJ7KF.d.mts} RENAMED
@@ -47,9 +47,10 @@ type StorageService = {
47
47
  *
48
48
  * **`contentType` and `contentLength` are signed, not advisory.** They are
49
49
  * part of the signature, so a client sending different ones is refused by the
50
- * store: the URL grants exactly one write, of exactly that many bytes, of
51
- * exactly that type. `contentLength` is therefore required — an unsigned
52
- * length would hand out an unbounded write, and there is no ceiling a
50
+ * store. The same URL can write the key repeatedly until expiry, replacing
51
+ * the previous object with different bytes of that size and type. Neither
52
+ * signed header proves the bytes. `contentLength` is required — an unsigned
53
+ * length would allow an unbounded single write, and there is no ceiling a
53
54
  * presigned PUT can express other than the exact number.
54
55
  *
55
56
  * The application still decides every input: whether this caller may write
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@btravstack/storage",
3
- "version": "0.19.0",
3
+ "version": "0.20.0",
4
4
  "description": "A Storage port for @btravstack/core: an in-memory adapter, an S3-compatible adapter with presigned reads, and a composition that spans, counts and logs every operation",
5
5
  "keywords": [
6
6
  "dependency-injection",
@@ -55,11 +55,11 @@
55
55
  "devDependencies": {
56
56
  "@aws-sdk/client-s3": "3.1146.0",
57
57
  "@aws-sdk/s3-request-presigner": "3.1146.0",
58
- "@btravstack/config": "0.19.0",
59
- "@btravstack/core": "0.19.0",
60
- "@btravstack/di": "0.19.0",
58
+ "@btravstack/config": "0.20.0",
59
+ "@btravstack/core": "0.20.0",
60
+ "@btravstack/di": "0.20.0",
61
61
  "@btravstack/internal-test-infra": "0.0.0",
62
- "@btravstack/observability": "0.19.0",
62
+ "@btravstack/observability": "0.20.0",
63
63
  "@btravstack/tsconfig": "0.4.0",
64
64
  "@opentelemetry/api": "1.9.1",
65
65
  "@opentelemetry/sdk-metrics": "2.11.0",
@@ -76,9 +76,9 @@
76
76
  "peerDependencies": {
77
77
  "@aws-sdk/client-s3": "^3.1000.0",
78
78
  "@aws-sdk/s3-request-presigner": "^3.1000.0",
79
- "@btravstack/config": "^0.19.0",
80
- "@btravstack/core": "^0.19.0",
81
- "@btravstack/di": "^0.19.0",
79
+ "@btravstack/config": "^0.20.0",
80
+ "@btravstack/core": "^0.20.0",
81
+ "@btravstack/di": "^0.20.0",
82
82
  "unthrown": "^5.0.0"
83
83
  },
84
84
  "peerDependenciesMeta": {