Suggests duplicate release PR in between time release PR merged and release created

[bcoe]

I noticed that when using the release-please app, there's a race condition, such that an identical release PR is created before a release is tagged:

Refs: googleapis/nodejs-network-security#27

[chingor13]

Weird, I would expect

release-please/src/manifest.ts

Lines 577 to 585 in d29eda1

	// if there are any merged, pending release pull requests, don't open
	// any new release PRs
	const mergedPullRequestsGenerator = this.findMergedReleasePullRequests();
	for await (const _ of mergedPullRequestsGenerator) {
	logger.warn(
	'There are untagged, merged release PRs outstanding - aborting'
	);
	return [];
	}

to catch that

[chingor13]

Note that findMergedReleasePullRequests() uses the GraphQL API so maybe there's a delay in indexing between when a pull request is merged and when it's returned by the GraphQL API.

[chingor13]

Downgrading to p2 to see if 3101 fixed it

[chingor13]

We haven't seen this recently in the app, closing for now.