You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found that a few PRs made back in 2022 were merged into master instead of main and now the two histories (and versions) differ. I didn't piece the timeline together but what I assume happened was a few PRs were opened against master and the repo changed default branches.
Specifically a race condition fixed in #294 got merged into master and never made it to main.
The way I found this was a project I'm working on uses v0.0.0-20220403145359-8e850b710d6d and I had trouble finding that hash version until it occurred to check the master branch which may have been default at the time.
The text was updated successfully, but these errors were encountered:
Question.
I found that a few PRs made back in 2022 were merged into
master
instead ofmain
and now the two histories (and versions) differ. I didn't piece the timeline together but what I assume happened was a few PRs were opened againstmaster
and the repo changed default branches.Specifically a race condition fixed in #294 got merged into
master
and never made it tomain
.The way I found this was a project I'm working on uses
v0.0.0-20220403145359-8e850b710d6d
and I had trouble finding that hash version until it occurred to check themaster
branch which may have been default at the time.The text was updated successfully, but these errors were encountered: