@synthetic-ai/premiere-mcp 1.1.8 → 2.1.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 +24 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,6 +1,29 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
-
## [
|
|
3
|
+
## [v2.1.0] — CRITICAL: correct the version line, ship everything since 2.0.0
|
|
4
|
+
|
|
5
|
+
`@synthetic-ai/premiere-mcp@2.0.0` (published 2026-06-10, the npm rename
|
|
6
|
+
from unscoped `premiere-pro-mcp`) has been the only version ever actually
|
|
7
|
+
published to the registry — `npm view` confirms `dist-tags.latest` and the
|
|
8
|
+
full `versions` list both show only `2.0.0`, right up until this release.
|
|
9
|
+
Six commits after the rename (v1.1.2 through v1.1.8, including v1.1.7's
|
|
10
|
+
**server-side license enforcement**) bumped `package.json`'s version
|
|
11
|
+
*backward* into a stale pre-rename 1.1.x line instead of continuing from
|
|
12
|
+
2.0.0, and were committed/tested but never `npm publish`ed under that
|
|
13
|
+
wrong version number. Net effect: every customer running
|
|
14
|
+
`npx @synthetic-ai/premiere-mcp` has been getting the unmodified 2.0.0
|
|
15
|
+
tarball — with **zero license checking on any of the 437 tools** — for
|
|
16
|
+
over three months, discovered 2026-09-23 while shipping the macOS preset
|
|
17
|
+
fix below. This release corrects the version line (2.0.0 → 2.1.0, a real
|
|
18
|
+
semver increase) and ships every accumulated fix at once:
|
|
19
|
+
- License enforcement (was v1.1.7): every tool except `ping` /
|
|
20
|
+
`get_version_info` now validates `PREMIERE_PRO_MCP_LICENSE`.
|
|
21
|
+
- In-panel auto-update + local license storage (was v1.1.2).
|
|
22
|
+
- ExtendScript obfuscation breaking `evalFile()` (was v1.1.4).
|
|
23
|
+
- Bridge could wedge forever after a single failed command read (was v1.1.5).
|
|
24
|
+
- macOS default sequence-preset paths (was v1.1.8, see below).
|
|
25
|
+
|
|
26
|
+
## [v1.1.8] — macOS default preset paths (superseded by v2.1.0, never actually reached "latest" — see above)
|
|
4
27
|
|
|
5
28
|
`create_sequence`, `create_sequence_from_clip`, and `get_default_sequence_presets`
|
|
6
29
|
only ever probed Windows install paths for the default `.sqpreset` (and, for
|
package/package.json
CHANGED