Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
v2.7.3 release
See original GitHub issue@webmakersteve since there was confusion regarding version v2.7.2 that was published as v2.7.1-2 (#663) and since we didn’t hear from you for a few months, I decided to merge #665 that solves Node 12 incompatibility. I also fixed e2e tests, improved and fixed travis ci tests and updated librdkafka to 1.2.1 (#684).
I was hoping that travis will execute npm publish since that stage seems well defined in .travis.yaml. I figured that the latest tag will be used as npm version when publishing and that this tag should point to the latest commit as well to bypass -x version suffix (which represents the number of commits between the latest tag and the latest commit).
Finally, I decided to try to trigger npm publish by tagging the latest commit with v2.7.3 but as I expected that didn’t work. It looks like you’ll again have to manually publish this version but be aware of .vscode (#670)
Hope this makes sense.
Update:
I fixed travis deployment stage but provided API key for NPM apparently doesn’t work.
I’ll now delete v2.7.3 tag. We’re stuck until @webmakersteve comes back.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:14 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Node12 has moved into LTS,We need a version to support it.
v2.7.3 is now published 🎆