ur-agent 1.64.0 → 1.64.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 +17 -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,22 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 1.64.1
|
|
4
|
+
|
|
5
|
+
- Fixed `npm install -g ur-agent` failing with
|
|
6
|
+
`No matching version found for playwright-core@^1.64.0`. Releases 1.61.2,
|
|
7
|
+
1.62.0, 1.63.0 and 1.64.0 were uninstallable: the version bump was a
|
|
8
|
+
`sed 's/OLD/NEW/g' package.json`, and `playwright-core` happened to sit at
|
|
9
|
+
`^1.61.1` — the same version UR was on — so the substitution rewrote the
|
|
10
|
+
dependency too, then cascaded with every later bump to a version that does
|
|
11
|
+
not exist. The built artifact and every test were fine; only `npm install`
|
|
12
|
+
failed, on other people's machines.
|
|
13
|
+
- Version bumping is now `scripts/version-bump.mjs`, which edits JSON files as
|
|
14
|
+
JSON and touches only the top-level `version` key, and uses anchored patterns
|
|
15
|
+
for text files that cannot match a dependency range.
|
|
16
|
+
- Added `test/dependencyIntegrity.test.ts`: no dependency range may equal the
|
|
17
|
+
UR version, which is the exact fingerprint of a bump that matched too much.
|
|
18
|
+
Verified it fails when the historical break is reintroduced.
|
|
19
|
+
|
|
3
20
|
## 1.64.0
|
|
4
21
|
|
|
5
22
|
- Tool-result pruning now announces itself. It changed context silently, so
|