Comparing v8.1.0...v8.1.1 · peter-evans/create-pull-request (original) (raw)

Commits on Feb 1, 2026

1. Configuration menu
   Browse the repository at this point in the history

Commits on Feb 28, 2026

1. Configuration menu
   Browse the repository at this point in the history

Commits on Mar 1, 2026

1. 12 Configuration menu
   Browse the repository at this point in the history

Commits on Mar 5, 2026

1. Configuration menu
   Browse the repository at this point in the history

Commits on Mar 14, 2026

1. Configuration menu
   Browse the repository at this point in the history

Commits on Mar 20, 2026

1. Configuration menu
   Browse the repository at this point in the history

Commits on Mar 25, 2026

1. Configuration menu
   Browse the repository at this point in the history

Commits on Mar 27, 2026

1. Configuration menu
   Browse the repository at this point in the history

Commits on Apr 1, 2026

1. Configuration menu
   Browse the repository at this point in the history

Commits on Apr 10, 2026

1. fix: retry post-creation API calls on 422 eventual consistency errors (…
   …#4356)
   Add retry logic to handle GitHub API eventual consistency errors that
   can occur after creating a new pull request. Follow-up API calls for
   milestones, labels, assignees, and reviewers may fail with a 422
   "Could not resolve to a node" error before the PR is fully propagated.

• Add generic retryWithBackoff helper in src/utils.ts with
  exponential backoff (default 2 retries, starting at 1s delay)
• Wrap post-creation API calls in src/github-helper.ts with
  withRetryForNewPr(), which only retries for newly created PRs
• Use @octokit/request-error RequestError type for precise error
  matching (status 422 + "Could not resolve to a node" message)
• Add unit tests for retryWithBackoff covering success, retry,
  exhaustion, and non-retryable error scenarios
• Update dist/index.js bundle and package.json dependencies
  
  Configuration menu
  Browse the repository at this point in the history