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.
Use the upcoming version in 'ver' actions on our dev branch
See original GitHub issueMotivation
Currently, we search-and-replace the ver actions before releasing. So while developing 3.4.0, our rules are still mentioning ver 3.3.0. This makes it harder to distinguish in logs whether a node is running the 3.3.0 release, or a 3.4.0 pre-release.
Proposed solution
Change our release procedure to increase the ver actions on the dev branch right after a release.
And create a PR to increase them right now to 3.4.0 for the v3.4/dev branch.
Alternatives
Don’t do it and keep the old versions.
Additional context
N/A
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (10 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
Closing this in favor of PR #2100.
Thanks to Airween’s version change utility added in #2085, version changes are now super easy and safe to make, which prevents bugs such as in #2009.
See PR #2085.