Rev version to 0.8.2 now that 0.8.1 is published.

[brendandburns]

@itowlson @drubin

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: brendandburns

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [brendandburns]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[itowlson]

Should we regenerate package-lock.json to match before merging?

[drubin]

Should we regenerate package-lock.json to match before merging?

Yes, we should. I added a "test" for this but I didn't take into account CI first runs npm ci which updates the package-lock.json will add a basic test before we run npm ci

[drubin]

@brendanburns Also any chance we can make it part of the release process to also add a github release? many people subscribe to only releases so they can be notified when we publish new releases?

I noticed we haven't published a release since 0.7.0 https://github.com/kubernetes-client/javascript/releases

[brendandburns]

@drubin Yeah, that's a good point. I filed #208 to track this.

[drubin]

Thanks @brendandburns

[brendandburns]

@drubin I sent #210 to improve things. Any chance we can merge this PR?

Thanks!

[drubin]

@brendandburns the package-lock.json still needs to be updated(else every time you npm install you will get a dirty tree) .

If you set that also to 0.8.2 it should be good to merge.

[brendandburns]

oops, good reminder. Fixed.

[brendandburns]

@drubin is there a way for us to extend our CI/CD so that it would fail in situations like this?

[drubin]

/lgtm

Will submit a pr when I get a second just kinsa busy this week end