-
Notifications
You must be signed in to change notification settings - Fork 228
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
feat: publish to npm for master branch #308
Conversation
I don't have sure about this workflow being automated before fixing problems already known by the last version tried to be published. |
I wasn't sure why it was commented out. Do you know what issue was there? |
Is it possible to merge this? This repo has not had a release in over 1 year. |
Yes, actually I'm the one looking and trying to take care of this repo. I'm preparing to list the principal issues to be fixed and prepare the next major release for the lib. Also, I want to publish the docs of swagger-jsdoc moving from the readme to a docusaurus page. If someone is interested in to help this feel free to contact me. |
The good news is that npm has the latest version, but github is not updated with new release version (but tag v6.2.0 is there). npm: https://www.npmjs.com/package/swagger-jsdoc |
Publish changes to npm repository. Calling it a feat since from what I've seen in the commits, there's been features introduced worthy of a minor version bump.