0.9.0

[IevgenRagulin]

@mdlavin , do you know if this is the correct process to release new package version?

I think previously we had to run these 2 commands on master locally:

npm version minor git push --follow-tags

We don’t have access to push to master any more, do we just submit a PR with new version as we are doing for bitbucket/old jenkins?

[coveralls]

Pull Request Test Coverage Report for Build 227

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 100.0%

---

Totals
Change from base Build 223:	0.0%
Covered Lines:	114
Relevant Lines:	114

---

💛 - Coveralls

[mdlavin]

Do we just submit a PR with new version as we are doing for bitbucket/old jenkins?

That's what I've been doing for other projects and it's worked. If it doesn't work here, then we'll have to update the project scripts