Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why do main and v2.0.0 diverge? #253

Closed
nvmnghia opened this issue Jan 30, 2023 · 5 comments
Closed

Why do main and v2.0.0 diverge? #253

nvmnghia opened this issue Jan 30, 2023 · 5 comments

Comments

@nvmnghia
Copy link

nvmnghia commented Jan 30, 2023

This is not a bug report, just a question. My code works in main, but not in v2.0.0, maybe due to some babel upgrade. After bisecting, I found out that main doesn't contain v2.0.0 at all. Why is this the case? Which one should I use?

@leineveber
Copy link
Collaborator

What do you mean by main doesn't contain 2.0.0? I see that main includes 2.0.0 by commits + a few more commits.

Please use main branch if you have problems with 2.0.0

@nvmnghia
Copy link
Author

nvmnghia commented Feb 3, 2023

@leineveber this is the v2 commit. Github says it's not contained in any branch.

@leineveber
Copy link
Collaborator

@nvmnghia
I see in main commits that its contained there

@nvmnghia
Copy link
Author

nvmnghia commented Feb 3, 2023

Oh I see. Tip of v2 and main are 2 different commits, though they may have the same content. Running

git log | grep $(git rev-list -n 1 tags/v2.0.0)

on main also yields nothing. Did you rebase v2 on top of somewhere in main? Anyway I still think this is weird.

@leineveber
Copy link
Collaborator

@nvmnghia
Just made a new release - 2.1.0. Please use it instead of 2.0.0

@nvmnghia nvmnghia closed this as completed Feb 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants