CHANGELOG: add missing changelogs

[spzala]

related #11184 #11211 #11354

[spzala]

/cc @jingyih

[spzala]

Hi @jingyih - updating changelog here per our discussion in the #11354 Thanks!

[codecov-io]

Codecov Report

Merging #11411 into master will decrease coverage by 0.74%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #11411      +/-   ##
==========================================
- Coverage   64.58%   63.84%   -0.75%     
==========================================
  Files         403      403              
  Lines       37969    37969              
==========================================
- Hits        24522    24240     -282     
- Misses      11814    12091     +277     
- Partials     1633     1638       +5

Impacted Files	Coverage Δ
client/client.go	42.81% <0%> (-30.72%)	⬇️
client/keys.go	70.35% <0%> (-21.11%)	⬇️
auth/range_perm_cache.go	48.1% <0%> (-12.66%)	⬇️
clientv3/naming/grpc.go	63.15% <0%> (-12.29%)	⬇️
proxy/grpcproxy/register.go	69.44% <0%> (-11.12%)	⬇️
auth/store.go	51.97% <0%> (-10.61%)	⬇️
clientv3/namespace/watch.go	87.87% <0%> (-6.07%)	⬇️
pkg/netutil/netutil.go	63.11% <0%> (-5.74%)	⬇️
proxy/grpcproxy/watcher.go	89.79% <0%> (-4.09%)	⬇️
clientv3/leasing/txn.go	88.09% <0%> (-3.18%)	⬇️
... and 18 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d1139d3...a45b997. Read the comment docs.

[jingyih]

IIUC, the fix is for parsing IPv6 in etcd client, not necessarily related to client balancer failover. So maybe something like Fix IPv6 endpoint parsing in client?

Given that they are bug fixes, maybe put these under section client v3 instead of breaking changes?

[spzala]

@jingyih sure, sounds good. Thanks!!

[jingyih]

@gyuho @jpbetz could you help take a look?

[gyuho]

Can we name the section "Package clientv3"

[spzala]

Can we name the section "Package clientv3"

Hi @gyuho thanks and I believe you are referencing changelog 3.3 and 3.4? If so, yes, I am fine with it but originally I put client v3 to keep it consistent with other places in the 3.3 and 3.4. (for example,
https://github.com/etcd-io/etcd/blob/master/CHANGELOG-3.3.md#client-v3
https://github.com/etcd-io/etcd/blob/master/CHANGELOG-3.3.md#client-v3-2
https://github.com/etcd-io/etcd/blob/master/CHANGELOG-3.3.md#client-v3-3
https://github.com/etcd-io/etcd/blob/master/CHANGELOG-3.4.md#client-v3
) So please let me know if you want to keep it as such or change it? Thanks!

[gyuho]

oh ok. then this looks good as well

[spzala]

oh ok. then this looks good as well

OK Thanks @gyuho !!