Skip to content

registry: re-pin lens to profiling-summary@3 (autolens_profiling#442 PR 4) - #74

Merged
Jammy2211 merged 3 commits into
mainfrom
feature/likelihood-lifecycle-p0-profiling
Oct 24, 2026
Merged

Jammy2211 merged 3 commits into
mainfrom
feature/likelihood-lifecycle-p0-profiling

Conversation

@Jammy2211

Copy link
Copy Markdown
Contributor

Summary

One-line registry change: the lens instance moves from profiling-summary@2 to profiling-summary@3, the contract this repo defined in #70. autolens_profiling#448 makes dashboard/catalogue.json emit v3 from the mirrored tree.

Merge order: autolens_profiling#448 first. Until it merges, main there still serves @2, so this PR's pyauto-pulse check is expected to be red on lens. After #448 merges, refetch the lens receipt on this branch (pyauto-pulse board, commit receipts and render), re-run CI, then merge. Between the two merges the lens receipt is invalid on main.

PR 3's catalogue already passes this checkout's v3 validator (build_catalogue --check --validate-with ../PyAutoPulse).

Test Plan

  • after autolens_profiling#448 merges: lens receipt refetched, pyauto-pulse check green

Refs PyAutoLabs/autolens_profiling#442

🤖 Generated with Claude Code

https://claude.ai/code/session_01SeDHwsR2dnwCk8Btfhej2L

Jammy2211 and others added 2 commits October 24, 2026 12:00
@Jammy2211
Jammy2211 merged commit 5f3ec2c into main Oct 24, 2026
2 checks passed
@Jammy2211
Jammy2211 deleted the feature/likelihood-lifecycle-p0-profiling branch October 24, 2026 11:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant