Skip to content

Commit 2288ac7

Browse files
authored
Merge pull request #5 from HAPNlab/chore/bump-psyexp-core
chore/bump-psyexp-core
2 parents cb85a52 + 251b76c commit 2288ac7

3 files changed

Lines changed: 2 additions & 17 deletions

File tree

docs/STANDARDIZATION.md

Lines changed: 0 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -12,21 +12,6 @@ would copy belongs in `psyexp-core`.**
1212

1313
---
1414

15-
## Open: align heat-task on the core manifest API
16-
17-
`psyexp-core` renamed `write_manifest(session_time=…)`
18-
`write_manifest(session_started_at=…)` in **0.8.0**. mid-task moved to 0.8.0 and
19-
the new kwarg; **heat-task is still on 0.7.0 and still passes `session_time=`**.
20-
So the two repos are pinned to different core majors and call the manifest writer
21-
differently.
22-
23-
**Action:** bump heat-task to `psyexp-core>=0.8.0` and rename its `write_manifest`
24-
call's kwarg to `session_started_at`; then bump to `0.9.0` and replace its
25-
`task/phases.py` `wait_for_key`/`check_quit` with the core ones (mid-task already
26-
does this). Keep the per-run `psyexp_core_version` in every manifest so the
27-
resolved core is always recoverable. Treat the core's public signature as a shared
28-
contract: a rename is a coordinated bump across all task repos in the same batch.
29-
3015
## Deferred: candidate core extractions
3116

3217
Worth centralizing eventually, but not until a second consumer makes the dedup pay

pyproject.toml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ dependencies = [
1919
# (any uv sync reverts it — --inexact does NOT help; the core is in the lock):
2020
# uv pip install -e ../psyexp-core
2121
# uv run --no-sync ... # or: export UV_NO_SYNC=1 (see `just core-*`)
22-
"psyexp-core>=0.8.0",
22+
"psyexp-core>=0.9.0",
2323
"psychopy>=2026.1",
2424
"scipy>=1.11",
2525
"numpy>=1.26",

uv.lock

Lines changed: 1 addition & 1 deletion
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

0 commit comments

Comments
 (0)