JoshuaKGoldberg / JoshuaKGoldberg/create-typescript-app

🐛 Bug: Releases can become broken after two quick pushes to main again

Open
#2,153 2 comments 0 reactions 0 assignees View on GitHub
status: accepting prs type: bug
Dominant language
TypeScript
Stars
1.4k
Forks
89
Avg merge
1m
Merged PRs (30d)
3

Description

### Bug Report Checklist

- [x] I have tried restarting my IDE and the issue persists.
- [x] I have pulled the latest `main` branch of the repository.
- [x] I have [searched for related issues](https://github.com/JoshuaKGoldberg/create-typescript-app/issues?q=is%3Aissue) and found none that matched my issue.

### Expected

Pushing two "meaningful" commits -as in, ones that should cause a new package publish- to `main` should not cause failures. Both should be released in 1-2 packages on npm.

### Actual

The saga of #556 -> #862 continues: if two meaningful commits are pushed to `main` quickly, the release flow of the first one will fail to `git push` because the second is running.

See the build failures from, in order:

1. https://github.com/JoshuaKGoldberg/create-typescript-app/commit/fda4ec9d9624945476326d552af8462d6eb5b392
2. https://github.com/JoshuaKGoldberg/create-typescript-app/commit/b39ae009b36c80dfdc3f50745a404dba0e0b77b4

### Additional Info

I don't yet know how to solve this... but accepting PRs if someone does.

🎁

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.