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

0.2.2 was tagged but not published #284

Closed
8 tasks
mbargiel opened this issue Jan 31, 2023 · 9 comments
Closed
8 tasks

0.2.2 was tagged but not published #284

mbargiel opened this issue Jan 31, 2023 · 9 comments

Comments

@mbargiel
Copy link
Contributor

Operating System

  • Linux
  • Windows 7
  • Windows 10
  • MacOS
  • other:

NodeJS Version

  • 0.x
  • 4.x
  • 6.x
  • 7.x
  • other:

Tmp Version

N/A

Expected Behavior

Expected npmjs registry to have 0.2.2 as the latest release.

Experienced Behavior

0.2.2 was tagged (August 2022), but 0.2.1 is still the latest release on the npmjs registry. (Note that the package.json version was not changed to 0.2.2 before tagging, so you may need to move the tag or sacrifice 0.2.2 and go to 0.2.3).

Note: I saw the PR #281 to rewrite the whole library in TypeScript. I would strongly suggest that you first publish the fix that I contributed via #278 (basically the only code change in "v0.2.1...v0.2.2", I think) before doing this since not every JavaScript project is configured to work with TypeScript. Thanks!

@silkentrance
Copy link
Collaborator

@mbargiel thanks for the information. I don't know why it was tagged and the version field was not bumped to the actual version.

As for the typescript based rewrite: it will be transpiled to plain javascript so that every dependent can use it.

@silkentrance
Copy link
Collaborator

I think that we can safely delete the tag.

@mbargiel
Copy link
Contributor Author

Awesome, thanks for reassuring me 😁 You can close this Issue at your leisure then (unless you want to keep it as a reminder for making a release before the rewrite, since I saw there were some discussions and points to settle in that PR...? Anyway, your call!)

@silkentrance
Copy link
Collaborator

I have removed the invalid v0.2.2 tag since no release nor a deployed version on npm depended on it.

@silkentrance
Copy link
Collaborator

No problem. However, I am not able to publish a new version to npmjs.com.

@tenxliviu
Copy link

It does look like version 0.2.2 appears in the documentation and changelog, but can't be found on npm.

@silkentrance What do you mean when you say you are not able to publish a new version to npm?

kj800x added a commit to kj800x/localproxy that referenced this issue Mar 20, 2023
@stianjensen
Copy link

Does another maintainer have the permission to push it to npm?

@raszi
Copy link
Owner

raszi commented Jun 1, 2023

I missed this somehow. I am pushing to the npm repositories and I did not publish nor tag v0.2.2.

I can do the following days.

@raszi
Copy link
Owner

raszi commented Feb 29, 2024

Since then v0.2.2 and v0.2.3 were released.

@raszi raszi closed this as completed Feb 29, 2024
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

5 participants