chore: release v0.6.0

[antfu]

0.6.0

Great thanks to @pikax for #311, making most of the APIs better aligned with the latest vue-next.

BREAKING CHANGE

• The lazy option of watch has been replaced by the opposite immediate option, which defaults to false. (It's ignored when using the effect signature). more details (Adjust watch behaviour to match latest RFC update #266)
• Rename nonReactive to markRaw
• UnwrapRef types from vue-next this can cause some incompatibilities.

Bug Fixes

• Added missing reactivity API from vue-next, feat: adding missing reactivity api from vue-next #311, @pikax
• Fix return type of toRefs, Typing the return of toRefs #315,
• Fix incorrect ref typing, fix(type): fix incorrect ref unwrap #344, @antfu
• Binding context vm when using function without parentheses, fix: binding context vm when using function without parentheses  #148, @pikax
• computed: destroy helper vm of computed to prevent memleak, Fix(computed): destroy helper vm of computed to prevent memleak (fix #270) #277, @LinusBorg

Features

• Added unref(feat: add unref API to match API with vue3 #309), isReactive (Missing function isReactive #327), toRef (Missing function toRef #313), UnwrapRef (Missing UnwrapRef export #247)
• Added shallowReactive, shallowRef
• Added toRaw
• getCurrentInstance available on the lifecycle hooks (onMounted, etc)
• getCurrentInstance returns undefined when called outside setup instead of throwing exception

Types

• Align reactivity types with vue-next

[antfu]

I would like to see #277, #301, #241, #148 get merged and shipped into this update.

/cc @pikax, as I would very possible to miss something, can you help me to check if the changelog covers #311 well? Thanks!

[pikax]

Missing this:

Breaking Change

• Rename nonReactive to markRaw
• UnwrapRef types from vue-next this can cause some incompatibilities.

Features

• Add toRaw
• getCurrentInstance available on the lifecycle hooks (onMounted, etc)
• getCurrentInstance returns undefined when called outside setup instead of throwing exception

Types

• Align reactivity types with vue-next

[antfu]

@pikax Updated. Thanks!

[antfu]

I think we are ready for this release.

@yyx990803 May I have the npm right for this package? (username: antfu) Or should I ask one of the members to help with publishing? Thanks.

[pikax]

LGTM

[LinusBorg]

I can push a release as well.

[antfu]

@LinusBorg Merged. If anything is alright, can you help with publishing? Thanks!

[pikax]

Btw I'm doing a PR in a bit to fix the PropType, should we hold it for 0.6.1?

[antfu]

@pikax yeah, I think it's good to hold it for the next release. Hope we can make this package iterates faster than it does now. :)

[haoqunjiang]

https://github.com/vuejs/composition-api/releases
Seems the version tag wasn't pushed to GitHub.

[antfu]

Yeah, it's haven't been published yet. @sodatea Can you help with that? I don't have the right to publish to npm for now. (I can handle the tag and Github release part) Done.

[LinusBorg]

@antfu I just published 0.6.0

[antfu]

@LinusBorg Great! Thanks!