@youdie006/prodex 0.40.24 → 0.40.25
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/dist/chatgpt-browser.js +4 -0
- package/docs/releasing.md +26 -0
- package/package.json +1 -1
package/dist/chatgpt-browser.js
CHANGED
|
@@ -1942,6 +1942,10 @@ export function chatGptThreadReadyExpression(conversationId) {
|
|
|
1942
1942
|
const current = new URL(location.href);
|
|
1943
1943
|
const match = /\\/c\\/([0-9a-f-]{16,})\\/?$/i.exec(current.pathname);
|
|
1944
1944
|
if (current.origin !== "https://chatgpt.com" || match?.[1].toLowerCase() !== ${JSON.stringify(conversationId.toLowerCase())}) return false;
|
|
1945
|
+
// A thread document that is still loading already has its URL and the
|
|
1946
|
+
// server-rendered editor, but no file inputs or messages yet (measured:
|
|
1947
|
+
// 0.6 s after navigating, complete at 6.7 s).
|
|
1948
|
+
if (document.readyState !== "complete") return false;
|
|
1945
1949
|
return Boolean(findChatGptComposerCandidate());
|
|
1946
1950
|
})()`;
|
|
1947
1951
|
}
|
package/docs/releasing.md
CHANGED
|
@@ -16,6 +16,32 @@ Release target: `v0.40.13` on `main`. The GitHub Release records the resolved co
|
|
|
16
16
|
|
|
17
17
|
The release adds a guarded, opt-in transition and more accurate blocker reporting. It does not claim that headless Pro consultation is verified on either deployment target or that authentication can be retained indefinitely.
|
|
18
18
|
|
|
19
|
+
## 0.40.24 Release Record
|
|
20
|
+
|
|
21
|
+
Release commit `e927eee` on `main` (cut after PR #14, merge `393f720`); tag `v0.40.24`.
|
|
22
|
+
|
|
23
|
+
**Publishing**
|
|
24
|
+
- `publish.yml` run 36975443077 passed all six platforms on the first attempt, then npm publish with SLSA v1 provenance and the GitHub Release (2026-10-02 07:10 UTC).
|
|
25
|
+
- `npm run release:verify` passed on the release commit after a build.
|
|
26
|
+
|
|
27
|
+
**What it fixes**
|
|
28
|
+
- Attachments into an existing conversation used a second form on the page that has no prompt editor.
|
|
29
|
+
|
|
30
|
+
**Installation on 2026-10-02**
|
|
31
|
+
- Global npm, each verified with `prodex --version` = 0.40.24.
|
|
32
|
+
- WSL, M3, Mac mini: installed. Running services were not restarted: 5 stdio MCP servers on WSL and 7 on M3 keep older code until their clients reconnect. The Mac mini had none running.
|
|
33
|
+
- M4: not reachable (hostname does not resolve); not updated.
|
|
34
|
+
|
|
35
|
+
**Live check after install (installed 0.40.24, shared WSL browser)**
|
|
36
|
+
- `--new-chat --attach` answered.
|
|
37
|
+
- `--continue --attach` failed with "composer has no file input" when the tab started on another conversation. When the tab was already on the target thread it had passed.
|
|
38
|
+
- Cause: the conversation page was used before it finished loading. Fixed in the next change.
|
|
39
|
+
|
|
40
|
+
**Browser container, same day**
|
|
41
|
+
- Image `sha256:2a2091354d90`, rebuilt from `b5eac7d` with the earlier uncommitted patches plus two more: the composer-form file input lookup and the loaded-document requirement for thread readiness.
|
|
42
|
+
- Full suite 1989 passed on the patched tree. The swap was gated on the send lock being free.
|
|
43
|
+
- Verified in the container: `--continue --attach` from another thread answered, and so did `--new-chat --attach`.
|
|
44
|
+
|
|
19
45
|
## 0.40.23 Release Record
|
|
20
46
|
|
|
21
47
|
Release commit `1c905e3` on `main` (cut after PR #13, merge `92c26ce`); tag `v0.40.23`.
|