Skip to content

Pin scheduled event processor to 1.0.0-dev.20261026.5 - #49725

Closed
Ray Chen (raych1) wants to merge 1 commit into
mainfrom
raych1-scheduled-processor-pin
Closed

Ray Chen (raych1) wants to merge 1 commit into
mainfrom
raych1-scheduled-processor-pin

Conversation

@raych1

Copy link
Copy Markdown
Member

Description

Pin the GitHub Event Processor install version in .github/workflows/scheduled-event-processor.yml from 1.0.0-dev.20260403.1 to the published 1.0.0-dev.20261026.5.

This version protects non-draft PRs whose titles start with the exact, case-sensitive prefix [AutoPR from stale labeling and closure. Draft AutoPRs retain normal stale handling. Related implementation: Azure/azure-sdk-tools#17403.

Only the scheduled processor version changes. Schedules, event.yml, event-processor.yml, and other pins are unchanged. No SDK packages or public APIs change.

Validation:

  • git diff --check — passed before commit.
  • go run github.com/rhysd/actionlint/cmd/actionlint@v1.7.12 -shellcheck= .github\workflows\scheduled-event-processor.yml — passed using the repository-pinned Actionlint version; ShellCheck was disabled because it is not installed locally.
  • Exact-content comparison against HEAD before commit — passed: the only changed file contains only the requested version replacement (one insertion and one deletion).
  • SDK builds/tests were not run because no SDK package changes are included. No live scheduled events were invoked.

If an SDK is being regenerated based on a new API spec, a link to the pull request containing these API spec changes should be included above.

All SDK Contribution checklist:

  • The pull request does not introduce [breaking changes]
  • CHANGELOG is updated for new features, bug fixes or other significant changes. N/A: workflow-only version pin; no SDK changes.
  • I have read the contribution guidelines.

General Guidelines and Best Practices

  • Title of the pull request is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

  • Pull request includes test coverage for the included changes. N/A: pin-only workflow edit; validation is documented above.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot AI balanced review requested due to automatic review settings October 27, 2026 17:50
@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 1 pipeline(s).
9 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

Copilot AI 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.

🟢 Approval recommended

The single-line version update matches the stated scope, with no identified issues requiring changes.

No open issues 🎉

What changed in this PR

Updates the scheduled GitHub Event Processor pin to adopt protection against stale labeling and closure for non-draft PRs with the exact, case-sensitive title prefix [AutoPR .

Changes:

  • Bumps the processor from 1.0.0-dev.20260403.1 to 1.0.0-dev.20261026.5.
  • Leaves schedules, other processor configuration, and SDK packages unchanged.
File Description
.github/​workflows/​scheduled-event-processor.yml Updates the installed processor version for the intended stale-handling behavior.

Review effort: Balanced

@github-actions

Copy link
Copy Markdown
Contributor
[Pilot] PR Pipeline Failure Analysis

What failed

The python - pullrequest check (Azure Pipeline build 7005791) failed at the "Build Analyze" stage, specifically in the Protected Files validation step that runs before build/test.

The PR modifies .github/workflows/scheduled-event-processor.yml (bumping the pinned GitHub Event Processor version). This file is covered by the repository's protected-files policy, which blocks direct changes to selected workflow and shared skill files under .github/ in this repo.

Relevant pipeline output
git diff "origin/main...4d60e5193599add1a0c63f08b5831b99e1164bf9" --name-only --diff-filter= -- '.github/workflows/*event*'
Here are the diff files:
    .github/workflows/scheduled-event-processor.yml
##[error]Changes to selected workflow and shared skill files under '.github/' should not be made in this Repo
.github/workflows/scheduled-event-processor.yml
##[error]Follow the workflow at https://github.com/Azure/azure-sdk-tools/blob/main/doc/engsys_workflows_and_skills.md
##[error]PowerShell exited with code '1'.

No test suite ran; the failed-test-results index is empty, confirming this is a pure validation/policy gate failure, not a test or build failure.

Recommended next steps

  • This is an intentional policy guard, not a bug: scheduled-event-processor.yml is a shared/managed workflow file that must be updated centrally (per https://github.com/Azure/azure-sdk-tools/blob/main/doc/engsys_workflows_and_skills.md), not via a direct PR edit in this repo.
  • Revert the change to .github/workflows/scheduled-event-processor.yml in this PR, and instead propagate the version pin update through the canonical shared-workflow sync process described in that doc.
  • If the version pin genuinely needs updating here outside that process, coordinate with the Engineering Systems team for an exception before re-attempting.
  • See https://aka.ms/ci-fix

Copilot detected the failing pipeline and generated the analysis above. To have it attempt a fix automatically, reply with @copilot please fix the failing pipeline on this PR.

Generated by Pipeline Analysis Next Steps · copilot · sonnet50 · 22.8 AIC · ⌖ 0.556 AIC · ⊞ 9.1K · ◷

@raych1

Copy link
Copy Markdown
Member Author

Closing in favor of updating the canonical scheduled event processor workflow in Azure/azure-sdk-tools and distributing it through the supported workflow sync pipeline.

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.

2 participants