# When can I expect the next release?

**URL:** <https://openziti.discourse.group/t/when-can-i-expect-the-next-release/805>\
**Category:** General Questions\
**Created:** [October 11, 2022, 2:23am UTC](https://openziti.discourse.group/t/when-can-i-expect-the-next-release/805 "2022-10-11T02:23:17Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![av-dev](https://avatars.discourse-cdn.com/v4/letter/a/ba8739/32.png) [@av-dev](https://openziti.discourse.group/u/av-dev)\
**Post date:** [October 11, 2022, 2:23am UTC](https://openziti.discourse.group/t/when-can-i-expect-the-next-release/805/1 "2022-10-11T02:23:17Z")

</div>

I believe the issue we encountered wrt externalId and x509-claims will be available in the next release ( v0.26.9? ). May I know when the next release will be?

TIA

---

<div class="post-metadata">

**Author:** ![plorenz](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/plorenz/32/54_2.png) [@plorenz](https://openziti.discourse.group/u/plorenz)\
**Post date:** [October 11, 2022, 2:47am UTC](https://openziti.discourse.group/t/when-can-i-expect-the-next-release/805/2 "2022-10-11T02:47:31Z")

</div>

Hi @av-dev, I’m working on getting the release out, should be this week unless something unexpected comes up.

Paul

---

<div class="post-metadata">

**Author:** ![plorenz](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/plorenz/32/54_2.png) [@plorenz](https://openziti.discourse.group/u/plorenz)\
**Post date:** [October 12, 2022, 8:00pm UTC](https://openziti.discourse.group/t/when-can-i-expect-the-next-release/805/3 "2022-10-12T20:00:59Z")

</div>

Hi @av-dev,  
The 0.26.9 release is out.

Cheers,  
Paul

---

<div class="post-metadata">

**Author:** ![av-dev](https://avatars.discourse-cdn.com/v4/letter/a/ba8739/32.png) [@av-dev](https://openziti.discourse.group/u/av-dev)\
**Post date:** [October 12, 2022, 8:01pm UTC](https://openziti.discourse.group/t/when-can-i-expect-the-next-release/805/4 "2022-10-12T20:01:26Z")

</div>

Perfect. Thank you so much.

---

<div class="post-metadata">

**Author:** ![av-dev](https://avatars.discourse-cdn.com/v4/letter/a/ba8739/32.png) [@av-dev](https://openziti.discourse.group/u/av-dev)\
**Post date:** [October 12, 2022, 10:14pm UTC](https://openziti.discourse.group/t/when-can-i-expect-the-next-release/805/5 "2022-10-12T22:14:49Z")

</div>

@plorenz I upgraded controller first , which went fine but when I tried to upgrade the first router, router kept crashing with following error -

```auto
[0.985] INFO fabric/router/xlink_transport.(*listener).bindSplitChannel |link, linkListener|: {routerId=[lAJSZUj5SG] linkProtocol=[tls] channelType=[ack] routerVersion=[v0.26.9] linkId=[4yNMqUFRqhB1pbg803Ox3T]} accepted part of split conn
[0.985] INFO fabric/router/handler_link.(*bindHandler).verifyRouter: {linkId=[4yNMqUFRqhB1pbg803Ox3T] routerId=[lAJSZUj5SG]} successfully verified router for link
[0.985] INFO fabric/router/handler_link.(*bindHandler).BindChannel: {routerId=[lAJSZUj5SG] routerVersion=[v0.26.9] linkId=[4yNMqUFRqhB1pbg803Ox3T]} link destination support heartbeats
[0.986] INFO fabric/router.(*xlinkAccepter).Accept: accepted new link [l/4yNMqUFRqhB1pbg803Ox3T]
[0.986] INFO fabric/router/xlink_transport.(*listener).bindSplitChannel |link, linkListener|: {linkId=[4yNMqUFRqhB1pbg803Ox3T] routerId=[lAJSZUj5SG] linkProtocol=[tls] channelType=[ack] routerVersion=[v0.26.9]} accepted link
[1.051] INFO fabric/router/xlink_transport.(*listener).bindSplitChannel |link, linkListener|: {routerVersion=[v0.26.9] linkId=[4yNMqUFRqhB1pbg803Ox3T] routerId=[lAJSZUj5SG] linkProtocol=[tls] channelType=[ack]} link registered
[1.085] INFO edge/tunnel/intercept.SetDnsInterceptIpRange: dns intercept IP range: 100.64.0.1 - 100.127.255.254
panic: runtime error: index out of range [12] with length 0

goroutine 48 [running]:
github.com/orcaman/concurrent-map/v2.ConcurrentMap[...].GetShard(...)
	github.com/orcaman/concurrent-map/v2@v2.0.0/concurrent_map.go:31
github.com/orcaman/concurrent-map/v2.ConcurrentMap[...].Get({0x0?, 0xe36a70?, 0x37e11d600?}, {0xc00097bcb0?, 0x7092bbeaed4c7?})
	github.com/orcaman/concurrent-map/v2@v2.0.0/concurrent_map.go:85 +0x13e
github.com/openziti/edge/router/xgress_edge_tunnel.(*servicePoller).requestServiceListUpdate(0xc000112280)
	github.com/openziti/edge@v0.24.7/router/xgress_edge_tunnel/servicepoll.go:122 +0x74
github.com/openziti/edge/router/xgress_edge_tunnel.(*servicePoller).pollServices(0xc000112280, 0xc0000c07e0?, 0xc0000b3140)
	github.com/openziti/edge@v0.24.7/router/xgress_edge_tunnel/servicepoll.go:108 +0x10a
created by github.com/openziti/edge/router/xgress_edge_tunnel.(*tunneler).Start
	github.com/openziti/edge@v0.24.7/router/xgress_edge_tunnel/tunneler.go:92 +0x80d

```

am I missing something here? TIA

---

<div class="post-metadata">

**Author:** ![av-dev](https://avatars.discourse-cdn.com/v4/letter/a/ba8739/32.png) [@av-dev](https://openziti.discourse.group/u/av-dev)\
**Post date:** [October 12, 2022, 10:21pm UTC](https://openziti.discourse.group/t/when-can-i-expect-the-next-release/805/6 "2022-10-12T22:21:54Z")

</div>

This is the process I followed to upgrade -

```auto
sudo systemctl stop router.service 
source ziti-cli-functions.sh
export ZITI_VERSION_OVERRIDE=v0.26.9
getZiti no
generateEnvFile
sudo systemctl start router.service

```

---

<div class="post-metadata">

**Author:** ![markamind](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/markamind/32/157_2.png) [@markamind](https://openziti.discourse.group/u/markamind)\
**Post date:** [October 12, 2022, 10:37pm UTC](https://openziti.discourse.group/t/when-can-i-expect-the-next-release/805/7 "2022-10-12T22:37:53Z")

</div>

Nice… that is much better than my manual process… thanks for sharing

---

<div class="post-metadata">

**Author:** ![plorenz](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/plorenz/32/54_2.png) [@plorenz](https://openziti.discourse.group/u/plorenz)\
**Post date:** [October 12, 2022, 10:43pm UTC](https://openziti.discourse.group/t/when-can-i-expect-the-next-release/805/8 "2022-10-12T22:43:49Z")

</div>

Thanks for the report, taking a look.

---

<div class="post-metadata">

**Author:** ![TheLumberjack](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/thelumberjack/32/113_2.png) [@TheLumberjack](https://openziti.discourse.group/u/TheLumberjack)\
**Post date:** [October 12, 2022, 11:25pm UTC](https://openziti.discourse.group/t/when-can-i-expect-the-next-release/805/9 "2022-10-12T23:25:32Z")

</div>

FWIW - we have an open “help make ziti better” type issue for the upgrade path. it’s on “the tod list” [provide 'upgrade' path for quickstart · Issue #779 · openziti/ziti · GitHub](https://github.com/openziti/ziti/issues/779)

---

<div class="post-metadata">

**Author:** ![plorenz](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/plorenz/32/54_2.png) [@plorenz](https://openziti.discourse.group/u/plorenz)\
**Post date:** [October 13, 2022, 2:16pm UTC](https://openziti.discourse.group/t/when-can-i-expect-the-next-release/805/10 "2022-10-13T14:16:09Z")

</div>

> <https://github.com/openziti/edge/issues/1209>
>
> see https://openziti.discourse.group/t/when-can-i-expect-the-next-release/805/5 …for reference
> 
> \`\`\`
> panic: runtime error: index out of range \[12\] with length 0
> 
> goroutine 48 \[running\]:
> github.com/orcaman/concurrent-map/v2.ConcurrentMap\[...\].GetShard(...)
> github.com/orcaman/concurrent-map/v2@v2.0.0/concurrent\_map.go:31
> github.com/orcaman/concurrent-map/v2.ConcurrentMap\[...\].Get({0x0?, 0xe36a70?, 0x37e11d600?}, {0xc00097bcb0?, 0x7092bbeaed4c7?})
> github.com/orcaman/concurrent-map/v2@v2.0.0/concurrent\_map.go:85 +0x13e
> github.com/openziti/edge/router/xgress\_edge\_tunnel.(\*servicePoller).requestServiceListUpdate(0xc000112280)
> github.com/openziti/edge@v0.24.7/router/xgress\_edge\_tunnel/servicepoll.go:122 +0x74
> github.com/openziti/edge/router/xgress\_edge\_tunnel.(\*servicePoller).pollServices(0xc000112280, 0xc0000c07e0?, 0xc0000b3140)
> github.com/openziti/edge@v0.24.7/router/xgress\_edge\_tunnel/servicepoll.go:108 +0x10a
> created by github.com/openziti/edge/router/xgress\_edge\_tunnel.(\*tunneler).Start
> github.com/openziti/edge@v0.24.7/router/xgress\_edge\_tunnel/tunneler.go:92 +0x80d
> \`\`\`

Fix should be out in 0.26.10 later today.

---

<div class="post-metadata">

**Author:** ![plorenz](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/plorenz/32/54_2.png) [@plorenz](https://openziti.discourse.group/u/plorenz)\
**Post date:** [October 13, 2022, 3:52pm UTC](https://openziti.discourse.group/t/when-can-i-expect-the-next-release/805/11 "2022-10-13T15:52:39Z")

</div>

0.26.10 has been released with a fix for the panic. Appreciate the quick testing and bug report @av-dev and let us know if you encounter any other issues.

Paul

---

<div class="post-metadata">

**Author:** ![av-dev](https://avatars.discourse-cdn.com/v4/letter/a/ba8739/32.png) [@av-dev](https://openziti.discourse.group/u/av-dev)\
**Post date:** [October 13, 2022, 3:55pm UTC](https://openziti.discourse.group/t/when-can-i-expect-the-next-release/805/12 "2022-10-13T15:55:23Z")

</div>

Awesome. Thank you for getting this out so quickly.  
I will upgrade in next few hours and get back in case of any issues.

---

<div class="post-metadata">

**Author:** ![johnalotoski](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/johnalotoski/32/570_2.png) [@johnalotoski](https://openziti.discourse.group/u/johnalotoski)\
**Post date:** [October 13, 2022, 6:58pm UTC](https://openziti.discourse.group/t/when-can-i-expect-the-next-release/805/13 "2022-10-13T18:58:47Z")

</div>

The update solved the panic for me in the new release. Thanks!

---

<div class="post-metadata">

**Author:** ![av-dev](https://avatars.discourse-cdn.com/v4/letter/a/ba8739/32.png) [@av-dev](https://openziti.discourse.group/u/av-dev)\
**Post date:** [October 13, 2022, 7:01pm UTC](https://openziti.discourse.group/t/when-can-i-expect-the-next-release/805/14 "2022-10-13T19:01:43Z")

</div>

yeah, same here. I did first router upgrade and watched logs, didnt see any issues. Proceeding with rest of them.
