ur-agent 1.64.0 → 1.65.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.
- package/CHANGELOG.md +32 -0
- package/dist/cli.js +11952 -1080
- package/documentation/index.html +1 -1
- package/extensions/jetbrains-ur/build.gradle.kts +1 -1
- package/extensions/vscode-ur-inline-diffs/package.json +1 -1
- package/package.json +2 -2
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,37 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 1.65.0
|
|
4
|
+
|
|
5
|
+
- The release gate now asks the registry whether the packed dependency ranges
|
|
6
|
+
can actually be installed. This is the check that was missing when 1.61.2
|
|
7
|
+
through 1.64.0 shipped uninstallable: the tarball built, the CLI started,
|
|
8
|
+
every test passed and the gate was green, because all of it ran against the
|
|
9
|
+
working tree and none of it asked npm whether `playwright-core@^1.64.0`
|
|
10
|
+
exists. The failure only ever appeared on a user's machine.
|
|
11
|
+
- A dependency range equal to the UR version is rejected outright, resolvable
|
|
12
|
+
or not. That equality is the fingerprint of a version bump that matched too
|
|
13
|
+
much, which is exactly how the break happened.
|
|
14
|
+
- Verified by reintroducing the historical break: exit 1 with
|
|
15
|
+
`playwright-core@^1.64.0 does not resolve: npm error code E404`, and exit 0
|
|
16
|
+
on a clean tree.
|
|
17
|
+
|
|
18
|
+
## 1.64.1
|
|
19
|
+
|
|
20
|
+
- Fixed `npm install -g ur-agent` failing with
|
|
21
|
+
`No matching version found for playwright-core@^1.64.0`. Releases 1.61.2,
|
|
22
|
+
1.62.0, 1.63.0 and 1.64.0 were uninstallable: the version bump was a
|
|
23
|
+
`sed 's/OLD/NEW/g' package.json`, and `playwright-core` happened to sit at
|
|
24
|
+
`^1.61.1` — the same version UR was on — so the substitution rewrote the
|
|
25
|
+
dependency too, then cascaded with every later bump to a version that does
|
|
26
|
+
not exist. The built artifact and every test were fine; only `npm install`
|
|
27
|
+
failed, on other people's machines.
|
|
28
|
+
- Version bumping is now `scripts/version-bump.mjs`, which edits JSON files as
|
|
29
|
+
JSON and touches only the top-level `version` key, and uses anchored patterns
|
|
30
|
+
for text files that cannot match a dependency range.
|
|
31
|
+
- Added `test/dependencyIntegrity.test.ts`: no dependency range may equal the
|
|
32
|
+
UR version, which is the exact fingerprint of a bump that matched too much.
|
|
33
|
+
Verified it fails when the historical break is reintroduced.
|
|
34
|
+
|
|
3
35
|
## 1.64.0
|
|
4
36
|
|
|
5
37
|
- Tool-result pruning now announces itself. It changed context silently, so
|