@heroiclands/package-build 0.6.0 → 0.6.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.
- package/CHANGELOG.md +37 -0
- package/package.json +3 -2
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,42 @@
|
|
|
1
1
|
# @heroiclands/package-build
|
|
2
2
|
|
|
3
|
+
## 0.6.1
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- e5cfbbb: Move the release workflow to `changesets/action@v2`.
|
|
8
|
+
|
|
9
|
+
v2 renamed four of the inputs this workflow passes — `version` →
|
|
10
|
+
`version-script`, `publish` → `publish-script`, `commit` → `commit-message`,
|
|
11
|
+
`title` → `pr-title` — and **rejects the old names outright** rather than
|
|
12
|
+
warning and carrying on. So the bump and the rename have to land in the same
|
|
13
|
+
commit.
|
|
14
|
+
|
|
15
|
+
Taken deliberately rather than waiting for Dependabot, because Dependabot bumps
|
|
16
|
+
the pin without touching the inputs, and that combination has already broken the
|
|
17
|
+
release pipeline in three sibling repositories:
|
|
18
|
+
Song-of-Heroic-Lands-FoundryVTT#1729, sohl-thalorna#71 and
|
|
19
|
+
sohl-kethira-basic#42. In the first of those it went unnoticed for over two
|
|
20
|
+
weeks — a failing release job looks exactly like a repository nobody has
|
|
21
|
+
released lately.
|
|
22
|
+
|
|
23
|
+
Nothing else had to move: `version-script` already calls an npm script (#25), and
|
|
24
|
+
one command is what v2's tokenized, never-shelled input requires.
|
|
25
|
+
- d4a5a6e: Take `@heroiclands/content-build` 1.8.2.
|
|
26
|
+
|
|
27
|
+
The declared range was `^1.0.0`, which permitted this all along — the lockfile
|
|
28
|
+
was the thing four minors behind, pinned at **1.4.0**. So the two packages were
|
|
29
|
+
built and tested against a version no consumer would actually resolve. Pinning
|
|
30
|
+
the range at `^1.8.2` and refreshing the lockfile makes what CI tests and what a
|
|
31
|
+
consumer installs the same thing.
|
|
32
|
+
|
|
33
|
+
The jump matters more than a patch bump suggests: package-build imports
|
|
34
|
+
`loadPackConfig` from `content-build/engine/pack-config`, and 1.4.0 predates
|
|
35
|
+
both the move to YAML configuration and the switch to lazy config accessors.
|
|
36
|
+
Verified against the new version rather than assumed — 293 tests pass,
|
|
37
|
+
`build:types` and `format:check` are clean, and the CLI resolves its
|
|
38
|
+
configuration and lists its commands.
|
|
39
|
+
|
|
3
40
|
## 0.6.0
|
|
4
41
|
|
|
5
42
|
### Minor Changes
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@heroiclands/package-build",
|
|
3
|
-
"version": "0.6.
|
|
3
|
+
"version": "0.6.1",
|
|
4
4
|
"description": "Shared toolchain for building and shipping a HeroicLands Foundry VTT package — manifest, localization, staging, bundle, release and deployment.",
|
|
5
5
|
"license": "GPL-3.0-or-later",
|
|
6
6
|
"type": "module",
|
|
@@ -84,11 +84,12 @@
|
|
|
84
84
|
"format:check": "prettier --check .",
|
|
85
85
|
"changeset": "changeset",
|
|
86
86
|
"changeset:check": "changeset status --since=origin/main",
|
|
87
|
+
"changeset:version": "changeset version && npm install --package-lock-only",
|
|
87
88
|
"prepare": "git config core.hooksPath .githooks || true"
|
|
88
89
|
},
|
|
89
90
|
"dependencies": {
|
|
90
91
|
"@foundryvtt/foundryvtt-cli": "^3.0.4",
|
|
91
|
-
"@heroiclands/content-build": "^1.
|
|
92
|
+
"@heroiclands/content-build": "^1.8.2",
|
|
92
93
|
"acorn": "^8.18.0",
|
|
93
94
|
"archiver": "^8.0.0",
|
|
94
95
|
"dotenv": "^17.2.3",
|