electron / electron/chromedriver
latest tag is applied to every release on npm
- Dominant language
- JavaScript
- Stars
- 143
- Forks
- 62
- Avg merge
- 8m
- Merged PRs (30d)
- 1
Description
This is an updated version of https://github.com/electron/chromedriver/issues/132. Apparently the issue still persists.
It looks like the latest tag is accidentally applied to every release. Currently v42.10.1 is tagged as the latest release which would be installed with npm i electron-chromedriver@latest. I think it should be v44.0.0 instead.
https://www.npmjs.com/package/electron-chromedriver?activeTab=versions
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by checking the npm versions page linked in the issue and compare the dist-tags for v42.10.1 and v44.0.0 with the repository's release or publishing process. Done means npm i electron-chromedriver@latest resolves to v44.0.0 while the published version history remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100