Tracking for N-API PRs needing backport

[mhdawson]

status	PR	description/branch	backports
complete
	nodejs/node#37652	Node-API 8
		master	nodejs/node@d154755
		v14.x
		v12.x	nodejs/node@93dd799
		v10.x	not planned
	nodejs/node#37195	add-on file name
		master	nodejs/node@ad3ebed
		v14.x	nodejs/node#37327
		v12.x	nodejs/node@f569209
		v10.x	not planned
	nodejs/node#35359	freeze/seal
		master	nodejs/node@19f1451
		v14.14.0	nodejs/node@c995242
		v12.20.0	nodejs/node@5faaa60
		v10.x	not planned
	nodejs/node#35266	napi_build_version
		master	nodejs/node@9868126
		v14.0.0	-"-
		v12.6.0	-"-
		v10.23.0	nodejs/node@b83f9a5
	nodejs/node#35214	more property defaults
		master	nodejs/node@c9506a8
		v14.12.0	nodejs/node@7f3b2b2
		v12.20.0	nodejs/node@d938e85
		v10.x	not planned
	nodejs/node#28237	type tagging
		master	nodejs/node@cc7ec88
		v14.8.0	nodejs/node@8cc9e5e
		v12.9.0	nodejs/node@e7486d4
		v10.x	not planned
	nodejs/node#34819	async cleanup hooks
		master	nodejs/node@0848f56
		v14.10.0	nodejs/node@3c32fe0
		v12.9.0	nodejs/node@a5aa3dd
		v10.x	not planned
	nodejs/node#35199	Node-API 7
		master	nodejs/node@31b3202
		v14.12.0	nodejs/node@ca11816
		v12.19.0	nodejs/node@b9d0f73
		v10.23.0	nodejs/node@54c2bc2
	nodejs/node#34045	wasm version
		master	nodejs/node@b327d33
		v14.5.0	nodejs/node@ac41bf0
		v12.18.3	nodejs/node@c0d6ff5
		v10.x	not planned
	nodejs/node#33597	wasm guards
		master	nodejs/node@b4ede54
		v14.5.0	nodejs/node@9148e01
		v12.18.3	nodejs/node@0a949c3
		v10.x	not planned

[legendecas]

Should we close this as it's all complete and create an issue for each new node-api version?

[mhdawson]

+1 makes sense to me.