This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit e26acc0:

Codecov Report

Merging #675 (e26acc0) into master (1bbac04) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master      #675   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           50        50           
  Lines          934       934           
  Branches       368       368           
=========================================
  Hits           934       934           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1bbac04...e26acc0. Read the comment docs.

I'm not sure about this. Basically the default branch can be named anything. So changing it doesn't really hurt.
On the other hand: Why change it at all as it is arbitrary and meaningless?
If you want to attribute any meaning, imho it should be renamed latest as it is our release branch to the latest channel.

So changing it doesn't really hurt.

We're already using main in most of our projects, so not renaming user-event's branch could cause confusion.

On the other hand: Why change it at all as it is arbitrary and meaningless?

The term master has a history in racism and is potentially offensive.

If you want to attribute any meaning, imho it should be renamed latest as it is our release branch to the latest channel.

While I personally like keeping default branches stable, commits in default branches are not necessarily published to npm (IIRC our chore commits aren't actually published until a commit after them needs to be published). Additionally, the git community (including GitHub's new repositories and Testing Library as a whole) is already moving to main, so I think it's best to be consistent. We'll keep the latest tag on npm because npm is not a version control system, so that's not directly related.

The term master has a history in racism and is potentially offensive.

I'm aware of this. I just don't agree.
Everything might be connoted and be offensive in a different context. But it's a different context.

are not necessarily published to npm (IIRC our chore commits aren't actually published until a commit after them needs to be published).

You're absolutely correct. But different areas on the same channel aren't something unheard of.
If you have a latest-branch, a latest-testing and a latest-build that doesn't necessarily mean your latest-package will at all time refer to the same commit. One could fail or in the case of chore commits decide that it is not necessary to relay it further.

We're already using main in most of our projects, so not renaming user-event's branch could cause confusion. [...]
Additionally, [...] Testing Library as a whole is already moving to main, so I think it's best to be consistent.

👍 Good enough for me if you guys feel strongly about this.

🎉 This PR is included in version 13.2.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀