Dashboard › publish › Distillation
11c2f237-1eb1-40cf-9af8-fe90f2473e0a["lore_tm_v1_0qzqolBc8NH45x4FZCMiywT82MjR43ksssZc6a58ELE","lore_tm_v1_FJt7BpSh4qR0seiKSOBZXZ5v4V8ecz70CmkH1z0UwSQ"]
src/publish/__tests__/publish-workflow.js contains 2 Vitest tests reading .github/workflows/publish.yml: (1) revalidates approval immediately before Craft asserts Revalidate approval attestation occurs after Set targets, before Publish using Craft, and its remaining workflow slice contains REQUIRE_CI_READY_ATTESTATION: "true"; (2) pins Craft to an immutable digest requires uses: docker://getsentry/craft@sha256:[a-f0-9]{64}.{/privacy} with /public in a GitHub user events_url URI template to retrieve only public events. Omitting {/privacy} retrieves public events plus private events when authenticated as that user.Authorization: Bearer <YOUR-TOKEN>, Accept: application/vnd.github+json, and X-GitHub-Api-Version: 2026-03-10.GET /user for the authenticated user; PATCH /user to update the authenticated user; GET /user/{account_id} using a durable account ID; GET /users to list personal and organization accounts in signup order; GET /users/{username} for public account information; and GET /users/{username}/hovercard for contextual information.GET /users pagination uses since exclusively; since returns IDs greater than the supplied user ID, while per_page defaults to 30 and has a maximum of 100.GET /users/{username}/hovercard accepts subject_type values organization, repository, issue, or pull_request; subject_type and subject_id require each other, and OAuth app tokens or classic personal access tokens require the repo scope.GET /users/{username}, private-profile followers and following values are 0 unless authenticated as that user; authentication as that user returns actual values even without OAuth scopes.404.