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
The latest commit in master according to both GitHub and git when I clone the repo is 495a4cf from July 2020. This leads to GitHub displaying the latest release as v7.21.5 from October 2020. However, I can see that the latest release on npm and from the tags is v7.23.2.
The master branch is not remotely out of date. Github (and git, by default) shows the commit authoring date, not the date the commit was landed. The latest commit - 495a4cf - was landed in #2713 23 hours ago, which you can see by clicking on the commit sha, and then on the linked PR.
You're right about the github releases; altho the tags are up to date, i haven't manually created a github release since v7.21.5. I've just updated them.
The latest commit in
master
according to both GitHub andgit
when I clone the repo is495a4cf
from July 2020. This leads to GitHub displaying the latest release asv7.21.5
from October 2020. However, I can see that the latest release onnpm
and from the tags isv7.23.2
.@ljharb
The text was updated successfully, but these errors were encountered: