Skip to content

Update release agent for automated release PRs - #621

Merged
Eduardo Villalpando Mello (edvilme) merged 1 commit into
mainfrom
docs-release-agent-guidance
Nov 11, 2026
Merged

Eduardo Villalpando Mello (edvilme) merged 1 commit into
mainfrom
docs-release-agent-guidance

Conversation

@edvilme

Copy link
Copy Markdown
Contributor

Summary

Update the existing .github/agents/release.agent.md to use the automated release-PR process instead of the obsolete manual stable-version, branch, tag, and follow-up development-bump sequence.

  • Prepare a PR changing only the root package.json development version; derive the previous even stable minor and full release/<STABLE_VERSION> ref.
  • Require an authorized PR creator, a genuine release-candidate plan on the latest head, publishing authorization, independent review, and required CI. Preserve the repository's squash auto-merge policy.
  • Explain automatic stable-branch creation after merge, Azure branch-triggered publishing, queue/status checks, Marketplace verification, and create-only recovery restrictions. Main already contains the next development version; no second bump PR is needed.
  • Preserve the agent's existing tool permissions and leave any configured GitHub tag/release creation to Azure.

This PR changes only release-agent documentation. It does not change manifests, workflows, action pins, or release refs and does not initiate another release. It does not deploy microsoft/vscode-python-ci#13; troubleshooting retains the warning about stale-base classification in older action pins. Python and Python Environments are outside this documentation rollout.

Validation

  • Prettier formatting and git diff --check passed.
  • Parsed YAML frontmatter and verified the tool list is unchanged.
  • Checked guidance against this repository's current plan, merged-release, and Azure stable-pipeline contracts.
  • Verified consistency across all six tool agents, allowing only repository identity and intentional merge-policy differences.
  • Documentation-only: no extension runtime tests required. The release plan should skip classification for this non-release PR.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 956d3afd-ae0b-486c-a60c-3a6276c23213
@rchiodo

Copy link
Copy Markdown
Contributor

🔒 Automated review in progress — Rich Chiodo (@rchiodo) is auto-reviewing this PR.

@rchiodo

Copy link
Copy Markdown
Contributor

Reviewed commit: bf7fb1f1befe7ff63a756a1bfce4fd98cfbd6467

Result: 🔵 not-applicable

Verification details

Verification: Automated verification is best effort. The PR author remains responsible for testing.

Summary: The supplied diff changes only release-agent documentation and adds no tests. The documented workflow names, merge trigger, Azure release-branch trigger, and publishing defaults match the repository configuration inspected. Runtime tests are not applicable; Git-based validation could not run because the container snapshot lacks Git metadata.

Test runs: 1 failed

  • ❌ Failed | unrelated to this PR | Batched environment and validation discovery | printf 'Sandbox profile: %s\n' "${AUTOMATION_SANDBOX_PROFILE:-unset}"; git status --short; git log -3 --oneline; git show --stat --oneline HEAD; git diff HEAD^ HEAD --name-only; git diff --check HEAD^ HEAD; node --version; python --version; if test -d node_modules; then printf 'node_modules present\n'; else printf 'node_modules absent\n'; fi; node -e 'const p=require("./package.json"); console.log(JSON.stringify({scripts:p.scripts,prettier:p.devDependencies?.prettier},null,2))'
❌ Batched environment and validation discovery diagnostic output
[container exit=0]
Sandbox profile: typescript
fatal: not a git repository (or any parent up to mount point /)
error: Could not access 'HEAD^'
v24.17.0
Python 3.13.18
node_modules absent
Declared prettier: ^3.8.1
The batched command exited zero, but its Git checks failed because repository metadata was unavailable. Formatting was not executed.

@rchiodo Rich Chiodo (rchiodo) left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved via Review Center.

@rchiodo Rich Chiodo (rchiodo) added the review-auto:approved Automated review: no blocking findings (approval posted). label Nov 11, 2026
@edvilme
Eduardo Villalpando Mello (edvilme) merged commit bb0d8df into main Nov 11, 2026
22 of 24 checks passed
@edvilme
Eduardo Villalpando Mello (edvilme) deleted the docs-release-agent-guidance branch November 11, 2026 00:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

debt review-auto:approved Automated review: no blocking findings (approval posted).

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants