Skip to content

chore: daily-upstream-check 2026-06-24 — cannot push branch (GitHub write access denied) #68

Description

@NativeTeachingAidsB

Daily upstream check 2026-06-24 — push blocked

The scheduled daily-upstream-check routine ran successfully and gathered all upstream version data, but could not push the results to GitHub because the session's GitHub integration returned 403 Resource not accessible by integration on all write operations (branch create, file push).

What was found (baseline — first run)

Source key Version fetched
claude-code-cli 2.1.187
claude-agent-sdk 0.3.187
claude-agent-sdk-py 0.2.108
codex-cli 0.142.0
cursor FAILED — cursor.com:443 blocked by egress proxy policy
cline FAILED — marketplace.visualstudio.com:443 blocked by egress proxy policy
continue FAILED — marketplace.visualstudio.com:443 blocked by egress proxy policy
windsurf FAILED — windsurf.com:443 blocked by egress proxy policy
zed v1.7.2
aider 0.86.2
goose 0.1.0
mcp-python 1.28.0
mcp-ts 1.29.0
mcp-spec d37097f42344@2026-06-24T01:47:57Z
claude-plugins-official bb335391eb83@2026-06-24T00:16:40Z

No PRs were needed (first run — all entries are baseline, no prior state to compare against).

Files prepared (not pushed)

  • docs/upstream-log/state.json — created with all baseline versions
  • docs/upstream-log/2026-06.md — created with today's run log entry

These were committed locally to branch chore/routines-daily-2026-06-24 but could not be pushed.

Action required

  1. Fix GitHub write access for the daily-upstream-check routine's session (needs Contents: write permission on the integration).
  2. Once fixed, manually push the prepared files from the local commit, or re-run the routine — it will recreate them correctly.
  3. Fix egress policy to allow cursor.com, marketplace.visualstudio.com, and windsurf.com if monitoring those sources is desired.

Auto-generated by daily-upstream-check routine.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions