Dashboard › craft › Session 1YZlyLc6IaSD
1YZlyLc6IaSDHoI5SRead-only research in /home/byk/Code/getsentry/publish on current master: map workflow/action code that accepts or dispatches Craft release work, issue parsing, labels, state keys, and tests. Do not edit. Return exact file:line citations, existing contract fields, safe additive workspace propagation design, and compatibility risks. Thoroughness medium.
/home/byk/Code/getsentry/publish/yarn.lock /home/byk/Code/getsentry/publish/vitest.config.js /home/byk/Code/getsentry/publish/package.json /home/byk/Code/getsentry/publish/auto-approve-repos.txt /home/byk/Code/getsentry/publish/README.md /home/byk/Code/getsentry/publish/LICENSE /home/byk/Code/getsentry/publish/AGENTS.md /home/byk/Code/getsentry/publish/.gitignore /home/byk/Code/getsentry/publish/.eslintrc.js /home/byk/Code/getsentry/publish/docs/rfc.md /home/byk/Code/getsentry/publish/docs/key_rotation_vault_changes.md /home/byk/Code/getsentry/publish/.github/CODEOWNERS /home/byk/Code/getsentry/publish/src/publish/update-issue.js /home/byk/Code/getsentry/publish/src/libs/github.js /home/byk/Code/getsentry/publish/.github/workflows/publish.yml /home/byk/Code/getsentry/publish/src/publish/post-workflow-details.js /home/byk/Code/getsentry/publish/src/publish/post-result.js /home/byk/Code/getsentry/publish/src/publish/inputs.js /home/byk/Code/getsentry/publish/src/modules/update-issue.js /...
security/remove-legacy-publish-state-write 1b279b935f2213dac175660877449772a2342dbb HEAD -> security/remove-legacy-publish-state-write, origin/security/remove-legacy-publish-state-write security: remove legacy publish-state-file write
master fatal: ambiguous argument 'master': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]'
origin/HEAD -> origin/main origin/add-agents-md origin/chore/fix-security-advisories origin/ci/switch-to-sentry-internal-app origin/docs/deprecate-action-prepare-release origin/docs/mermaid-release-flow origin/fix/add-packages-write-permission origin/fix/add-workflow-permissions origin/fix/auto-approve-token origin/fix/undici-security-vulnerability origin/fix/update-node-version-in-workflows origin/main origin/migrate-secrets origin/ref/remove-unused-requester-field origin/refactor/auto-approve-repo-list origin/remove/retract-command origin/security/dual-write-publish-state origin/security/remove-legacy-publish-state-write 2513c782a5a54da5921a87ce52fc357a78c8e263 refs/heads/chore/fix-security-advisories a58b7212cd8886308be5d742885271ebda2f81e7 refs/heads/fix/add-workflow-permissions 178160d3426aa72d95cd4d61b56162588e273f06 refs/heads/main 83d9383368ee750b828da30943768a1956966e4e ...
178160d3426aa72d95cd4d61b56162588e273f06 origin/main, origin/HEAD, main security: dual-write publish state file to safe location (#7886) .github/workflows/publish.yml | 25 ++++++++----------------- 1 file changed, 8 insertions(+), 17 deletions(-) .github/CODEOWNERS .github/workflows/auto-approve.yml .github/workflows/ci-poller.yml .github/workflows/cocoapods-keepalive.yml .github/workflows/publish.yml .github/workflows/test.yml README.md docs/key_rotation_vault_changes.md docs/rfc.md package.json src/libs/__tests__/github.js src/libs/github.js src/modules/__tests__/details-from-context.js src/modules/__tests__/post-workflow-details.js src/modules/__tests__/process-end-state.js src/modules/__tests__/update-issue.js src/modules/details-from-context.js src/modules/post-workflow-details.js src/modules/process-end-state.js src/modules/update-issue.js src/publish/inputs.js src/publish/post-result.js src/publish/post-workflow-details.js src/publish/update-issue.js
Found 100 matches (more matches available) /home/byk/Code/getsentry/publish/docs/rfc.md: Line 18: 4. Create a structured issue template to request releases Line 19: 5. Have a "release" action on each repo, that runs `craft prepare` to get the release branch ready and opens an issue on the release repo for publishing with the following information: Line 24: 7. The release then closes the issue with a success message Line 30: 2. Should release repo owners still need to create an issue to trigger a release, even if they mark it as approved themselves? (or should we always require a second person to approve, like a code review) Line 37: We can directly link to manual workflow triggers in the repos but GitHub does not allow pre-filling input values via the URL: [https://github.com/getsentry/sentry/actions/manual?workflow=.github%2Fworkflows%2Frelease.yml](https://github.com/getsentry/sentry/actions/manual?workflow=.github%2Fworkflows%2Frelease.yml) so we need to use the issue ...
Date: Aug 25, 2026 * 🔴 (10:32) User stated preference that releases should always require approval from a second person, analogous to code review. * 🟡 (10:32) Repository search results show `docs/rfc.md` frames whether release-repository owners may self-approve versus requiring a second approver as an unresolved design question; it also says GitHub manual-workflow URLs cannot prefill input valu…
Date: Aug 25, 2026 * 🟡 (10:31) `origin/main`, `origin/HEAD`, and local `main` all point to commit `178160d3426aa72d95cd4d61b56162588e273f06`, whose subject is `security: dual-write publish state file to safe location (#7886)`. * 🟡 (10:31) Commit `178160d3426aa72d95cd4d61b56162588e273f06` modifies `.github/workflows/publish.yml` only: 8 insertions and 17 deletions (25 changed lines). * 🟡 (10:31…
Date: Aug 25, 2026 * 🟡 (10:29) Git remote refs showed `origin/HEAD -> origin/main` and `origin/main`; therefore the repository’s remote default branch is `main`, not `master`. Other listed remote branches: `origin/add-agents-md`, `origin/chore/fix-security-advisories`, `origin/ci/switch-to-sentry-internal-app`, `origin/docs/deprecate-action-prepare-release`, `origin/docs/mermaid-release-flow`, `…
Date: Aug 25, 2026 * 🟡 [requested-read-only-research] (10:14) User requested medium-thoroughness, read-only research in `/home/byk/Code/getsentry/publish` on purported current `master`; requested mapping of workflow/action code that accepts or dispatches Craft release work, issue parsing, labels, state keys, and tests. User requested no edits and a return containing exact file:line citations, ex…