@_linked/s3 1.4.1 → 1.5.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 (2) hide show
  1. package/CHANGELOG.md +15 -0
  2. package/package.json +2 -2
package/CHANGELOG.md CHANGED
@@ -1,5 +1,20 @@
1
1
  # @\_linked/s3
2
2
 
3
+ ## 1.5.0
4
+
5
+ ### Minor Changes
6
+
7
+ - [#28](https://github.com/linked-fw/s3/pull/28) [`a3e2308`](https://github.com/linked-fw/s3/commit/a3e2308b78e2c8237eabd395f11d325f775360a3) Thanks [@flyon](https://github.com/flyon)! - Require `@_linked/core@^2.22.8` (was `^2.21.0`), and pin it in the lockfile.
8
+
9
+ The declared range was wide enough that the resolved core depended on whatever the
10
+ consumer — or this repo's own CI, via `package-lock.json` — happened to install. Core
11
+ decides how a shape's IRI is minted, so a stale core made this package emit legacy
12
+ `data.lincd.org` IRIs instead of the arch-02 `linked.cm` scheme. Which IRIs a published
13
+ package produces should not be a function of the installer's dependency tree.
14
+
15
+ Minor rather than patch: this raises the minimum core a consumer must resolve, so it
16
+ changes what gets installed rather than only what this package does internally.
17
+
3
18
  ## 1.4.1
4
19
 
5
20
  ### Patch Changes
package/package.json CHANGED
@@ -11,7 +11,7 @@
11
11
  "type": "git",
12
12
  "url": "git+https://github.com/linked-fw/s3.git"
13
13
  },
14
- "version": "1.4.1",
14
+ "version": "1.5.0",
15
15
  "packageManager": "npm@11.19.1",
16
16
  "linkedPackage": true,
17
17
  "type": "module",
@@ -38,7 +38,7 @@
38
38
  "aws"
39
39
  ],
40
40
  "dependencies": {
41
- "@_linked/core": "^2.21.0",
41
+ "@_linked/core": "^2.22.8",
42
42
  "@_linked/server": "^2.5.1",
43
43
  "@_linked/server-utils": "^1.0",
44
44
  "@aws-sdk/client-s3": "^3.159.0",