Hi,
Thank you for taking the time to respond and for your assistance.
I used exactly the same method via SSH with 19.07.03 and it did not fix the problem as I had to do the same with version 18.06.04. With version 18.06.04 and dsl_control stopped and disabled, I have not had a drop for 29 days since I downgraded. Also, more free memory is available for version 18.06.4 versus 19.07.03 and the Luci browser response for 18.06.04 is way faster than 19.07.03.
Note well: for both versions, I am not running additional packages.
I will stick with version 18.06.04.
Probably, my issues were caused by overheating. Although the router itself is physically placed on a cabinet and nothing is obscuring the ventilation grill in the body, it still felt rather hot at the touch. So I unplugged an external hard drive from the USB port, stopped some related services to lower CPU usage a bit (it had been far from 100% anyway), placed a couple of CD cases under the lags to ease ventilation, and since then the router has been running fine for 3.5 days now. I also have reverted the WiFi country code settings to default US but am not sure if this has had any effect. So my theory is that the older 18.06 releases put lower load on the system causing less heating. Then, at some point after I did a minor patch-release upgrade, some firmware components (probably the WiFI firmware, because it was the only component that changed significantly in the 18.06 branch) began to put higher load on the electronics which caused overheating and was distinctly visible as periodic hang ups.
I found that running firmware version 18.06.04 on a BT Home Hub 5a led to a temperature drop of a 14°C when compared to firmware version 19.07.03. This was monitored over a number of days. For the two firmware versions, I used Flash new firmware image and I did not keep the settings.
1 Like
Interesting, this is rather unexpected.
Please open a bug report with details and comparison in similar usage: load average, which processes use CPU in top, temperature. If possible test and compare several OpenWrt versions (18.06.X, 19.07.X, latest master) and variation of wireless driver and firmware (regular ath10k versus ath10k-ct versus no wireless at all)
It is likely related to ath10k. However, it could also be a general problem affecting all devices (caused by newer kernel or userspace process issue), althought that would be really surprising.
@briskycat your input is also welcome
Hi
my TP-LINK Archer C7 V5 (Firmware 1.0.11) does not accept the 19.0.3 factory.bin for a first install. Support for TP-LINK Archer C7 v5 (RU) says that the previous 19.0.2 works through the factory web gui, which i can confirm.
I suggest that you decrease the v5 factory.bin-link from 19.0.3 back to 19.0.2 at your website https://openwrt.org/toh/tp-link/archer-c7-1750 until its solved.
Did anybody have a successful UPGRADE to 19.0.3 on an Archer C7 V5, compared to an unsuccessful factory.bin fresh install?
Regards
1 Like
I upgraded with the result LUKS doesnt work on my x86 device Problems opening LUKS-devices on APU (x86) running latest version of OpenWRT
Anyone else has the same problem ?
I measured two different R7800 with very similar configuration. 18.06.8 / 19.07.3 both idleling and with non ct wireless driver, both about 10.6W
DFS channels are not working with 19.07.3 and the DLINK DIR-860L B1 (MT7621).
Wireless is not associated + the following syslog message:
daemon.notice netifd: radio0 (7271): WARNING (wireless_add_process): executable path /usr/sbin/wpad does not match process 6949 path ()
daemon.notice netifd: radio0 (7271): Device setup failed: HOSTAPD_START_FAILED
Actually only channel 36 is working which seems to be a bit odd. I've flashed the factory.bin of 19.07.3 via recovery and set up everything from the scratch, so there is no old config involved.
I guess it must be a driver related problem?
I am a new user currently on 19.07.02 which I installed in May. If I do a sysupgrade will I need to reinstall all of my packages again (Nord VPN, QOS, printer, attached storage and bandwidth monitor)? Also does it keep configuration files?
Thanks,
Chris.
Yes.
Typically yes, but it depends on where they are stored. If these live in /etc/config you are good to go, otherwise you might need to add them manually to /etc/sysupgrade.conf
Upgraded Netgear R8000 from 18.06.4 to 19.07.3 and 5GHz wifi is crashing every other day or so. Country code is US. Radio 2 is on channel 48. Radio 0 is on channel 149. Did an upgrade first, then also tried a clean/fresh install. Nothing else installed.
Unfortunately I can't physically access the router as it's installed at a family member's house over an hour away. I don't have access to logs, etc. Note that everything worked in 18.06.4.
After using the LuCI gui to run the upgrade to 19.07.3, will I then have to ssh into the router and reset the password? I have problems with re-entering the wifi passwords, too. I'm too much not computer literate to understand wep, wpa, wpa2-psk, and I've tried to learn my way around this, to not much success.
Gentleman (and undoubtedly some ladies), for an utter amateur as myself, I would dearly prefer to not be inside my router's workings at all. If I could but run the upgrade and run a backup to save the configuration, it would be so much less scary.
@MarkP2015 - If you keep settings during the update, you will not need to login to set passwords and such. However, keeping settings is only considered safe if you are performing a maintenance upgrade (i.e. 19.07.2 > 19.07.3). It is not recommended if you are upgrading across a major release such as from 18.06.x > 19.07.x. This recommendation is not to say that it won't work, but rather that it is plausible that there will be some changes under the hood that could result in the configuration incompatibilities -- this is especially true if you're making a large jump (say OpenWrt 15.05.x > 19.07.x, or if your router is Atheros 71xx based and has been migrated from the ar71xx to the ath79 target platform).
My guess is that you have a relatively simple configuration since it sounds like you aren't utilizing OpenWrt's advanced features and tinkering with stuff all the time. So even if you do need to log in to update things, you can probably do everything you need with the LuCI web interface in just a few minutes. The community here can also help you with this process by pointing you to the relevant documentation/tutorial pages (the quick start guide is really useful) or just describing the steps involved. For this, you may want to open a new thread.
What router are you using and what is the current version of OpenWrt?
Thank you, first of all. In response to your 2 questions.
From the login screen:
LuCI openwrt-19.07 branch (git-20.057.55219-13dd17f) / OpenWrt 19.07.2 r10947-65030d81f3
and this is the maintenance upgrade from 19.07.2 to 19.07.3 for a TP-Link Archer C7 version 2.0.
I have the downloaded filename as:
openwrt-19.07.3-ath79-generic-tplink_archer-c7-v2-squashfs-sysupgrade
However, reading about checksums at: https://openwrt.org/docs/guide-quick-start/verify_firmware_checksum:
"3. Check that the checksum string matches as the one you can find in the sha256sums field on the download page you retrieved by following the instructions above." Unfortunately, when I downloaded the above .bin, I was not take to a page with checksums. All that happened was a smaller window opened asking whether to Save the file.
As long as you are currently using an ath79 target, you can keep settings, no issues.
Hi, I am not having full speed in an attached USB 3.0 external hard drive using this release in a Linksys wrt3200acm, here is a measure:
root@OpenWrt:/mnt/sda4# time dd if=/dev/zero of=tempfile bs=1M count=1024
1024+0 records in
1024+0 records out
real 0m 26.26s
user 0m 0.00s
sys 0m 4.01s
Which is more or less 39MBps and according to this link my hardware is capable of 100MBps write speed on USB 3.0.
Maybe drivers are buggy?
P.D. this same external HDD on my desktop PC have 100MBps write speeds normally.
Since I reset the WiFi country code settings to default US a month ago my ZyXEL NBG6817 has been running uninterrupted without any major issues. The 5GHz radio module has rebooted once and switched from channel 48, for which it had been configured, to channel 100. I also found this in the kernel log afterwards:
[1482790.464483] device wlan0 left promiscuous mode
[1482790.464677] br-lan: port 3(wlan0) entered disabled state
[1482790.526047] ath10k_pci 0000:01:00.0: mac-vif-chan had error in htt_rx_h_vdev_channel, peer-id: 0 vdev-id: 0 peer-addr: 8c:59:73:f9:d4:39.
[1482790.528086] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482790.537837] ------------[ cut here ]------------
[1482790.543474] WARNING: CPU: 0 PID: 0 at /home/user/openwrt/build_dir/target-arm_cortex-a15+neon-vfpv4_musl_eabi/linux-ipq806x_generic/ath10k-ct-regular/ath10k-ct-2019-09-09-5e8cd86f/ath10k-4.19/htt_rx.c:906 ath10k_htt_t2h_msg_handler+0xf14/0x2124 [ath10k_core]
[1482790.549189] Modules linked in: pppoe ppp_async l2tp_ppp ath10k_pci ath10k_core ath pptp pppox ppp_mppe ppp_generic nf_conntrack_ipv6 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE cfg80211 xt_u32 xt_time xt_tcpudp xt_tcpmss xt_string xt_statistic xt_state xt_socket xt_recent xt_physdev xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_iprange xt_hl xt_helper xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_connbytes xt_comment xt_bpf xt_TRACE xt_TPROXY xt_TEE xt_TCPMSS xt_REDIRECT xt_NFQUEUE xt_NFLOG xt_NETMAP xt_LOG xt_LED xt_HL xt_FLOWOFFLOAD xt_DSCP xt_CT xt_CLASSIFY vhci_hcd usblp usbip_host usbip_core ums_usbat ums_sddr55 ums_sddr09 ums_karma ums_jumpshot ums_isd200 ums_freecom ums_datafab ums_cypress ums_alauda ts_kmp ts_fsm ts_bm slhc nft_set_rbtree nft_set_hash nft_reject_ipv6
[1482790.619719] nft_reject_ipv4 nft_reject_inet nft_reject nft_redir nft_quota nft_numgen nft_meta nft_log nft_limit nft_exthdr nft_ct nft_counter nft_chain_route_ipv6 nft_chain_route_ipv4 nfnetlink_queue nfnetlink_log nf_tables_ipv6 nf_tables_ipv4 nf_tables_inet nf_tables nf_socket_ipv6 nf_socket_ipv4 nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_conntrack_ipv4 nf_nat_ipv4 nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_dup_ipv6 nf_dup_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack_netlink iptable_raw iptable_mangle iptable_filter ipt_rpfilter ipt_ECN ip6table_raw ip6t_rpfilter ip_tables crc_ccitt compat br_netfilter arptable_filter arpt_mangle arp_tables fuse sch_cake act_connmark nf_conntrack sch_tbf sch_ingress sch_htb sch_hfsc em_u32 cls_u32 cls_tcindex cls_route
[1482790.690931] cls_matchall cls_fw cls_flow cls_basic act_skbedit act_mirred ledtrig_usbport xt_set ip_set_list_set ip_set_hash_netportnet ip_set_hash_netport ip_set_hash_netnet ip_set_hash_netiface ip_set_hash_net ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 ip_gre gre ifb sctp libcrc32c l2tp_netlink l2tp_core udp_tunnel ip6_udp_tunnel ip_tunnel tun vfat fat autofs4 dns_resolver nls_utf8 nls_koi8_r nls_iso8859_1 nls_cp437 nls_cp1251 sha1_generic md5 ecb uas usb_storage leds_gpio xhci_plat_hcd xhci_pci xhci_hcd dwc3 dwc3_of_simple ohci_platform ohci_hcd phy_qcom_dwc3
[1482790.762423] ahci ehci_platform sd_mod ahci_platform libahci_platform libahci libata scsi_mod ehci_hcd gpio_button_hotplug f2fs ext4 mbcache jbd2 exfat crc32c_generic crc32_generic
[1482790.784673] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.14.180 #0
[1482790.800822] Hardware name: Generic DT based system
[1482790.807016] [<c030f2c4>] (unwind_backtrace) from [<c030b498>] (show_stack+0x14/0x20)
[1482790.812215] [<c030b498>] (show_stack) from [<c07c2904>] (dump_stack+0x94/0xa8)
[1482790.819942] [<c07c2904>] (dump_stack) from [<c031f978>] (__warn+0xf0/0x11c)
[1482790.827484] [<c031f978>] (__warn) from [<c031fa64>] (warn_slowpath_null+0x20/0x28)
[1482790.834577] [<c031fa64>] (warn_slowpath_null) from [<bfa4443c>] (ath10k_htt_t2h_msg_handler+0xf14/0x2124 [ath10k_core])
[1482790.842559] [<bfa4443c>] (ath10k_htt_t2h_msg_handler [ath10k_core]) from [<bfa44678>] (ath10k_htt_t2h_msg_handler+0x1150/0x2124 [ath10k_core])
[1482790.853305] [<bfa44678>] (ath10k_htt_t2h_msg_handler [ath10k_core]) from [<bfa46254>] (ath10k_htt_get_rx_ring_size_64+0xc00/0xc48 [ath10k_core])
[1482790.866326] [<bfa46254>] (ath10k_htt_get_rx_ring_size_64 [ath10k_core]) from [<bfa469d0>] (ath10k_htt_txrx_compl_task+0x734/0xbe8 [ath10k_core])
[1482790.879212] [<bfa469d0>] (ath10k_htt_txrx_compl_task [ath10k_core]) from [<bfa9b758>] (ath10k_pci_napi_poll+0x7c/0x11c [ath10k_pci])
[1482790.892316] [<bfa9b758>] (ath10k_pci_napi_poll [ath10k_pci]) from [<c06ab6c8>] (net_rx_action+0x144/0x31c)
[1482790.904310] [<c06ab6c8>] (net_rx_action) from [<c03015c8>] (__do_softirq+0xf0/0x264)
[1482790.914288] [<c03015c8>] (__do_softirq) from [<c0323f2c>] (irq_exit+0xdc/0x148)
[1482790.922017] [<c0323f2c>] (irq_exit) from [<c0362ad8>] (__handle_domain_irq+0xa8/0xc8)
[1482790.929567] [<c0362ad8>] (__handle_domain_irq) from [<c0301488>] (gic_handle_irq+0x6c/0xb8)
[1482790.937378] [<c0301488>] (gic_handle_irq) from [<c030c08c>] (__irq_svc+0x6c/0x90)
[1482790.946052] Exception stack(0xc0b01f48 to 0xc0b01f90)
[1482790.953532] 1f40: 00000001 00000000 00000000 c0315200 ffffe000 c0b03cb8
[1482790.958753] 1f60: c0b03c6c 00000000 00000000 c0a2ea28 00000000 00000000 c0b01f90 c0b01f98
[1482790.967073] 1f80: c030862c c0308630 60000013 ffffffff
[1482790.975400] [<c030c08c>] (__irq_svc) from [<c0308630>] (arch_cpu_idle+0x38/0x44)
[1482790.980614] [<c0308630>] (arch_cpu_idle) from [<c0358928>] (do_idle+0xe8/0x1bc)
[1482790.988247] [<c0358928>] (do_idle) from [<c0358c70>] (cpu_startup_entry+0x1c/0x20)
[1482790.995810] [<c0358c70>] (cpu_startup_entry) from [<c0a00cd4>] (start_kernel+0x400/0x40c)
[1482791.003688] ---[ end trace 43952598b14b696b ]---
[1482791.011772] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.016635] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.022364] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.028252] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.033987] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.039886] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.046652] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.051431] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.057309] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.063071] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.068951] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.074761] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.080509] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.086386] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.092152] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.098035] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.103774] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.109658] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.115468] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.121221] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.127097] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.132853] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.138740] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.144552] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.150301] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.156177] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.161932] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.167825] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.173564] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.179446] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.185257] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.191013] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.196878] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.202645] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.208531] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.214341] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.220093] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.225969] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.231725] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.237615] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.243356] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.249236] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.255047] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.260804] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.266700] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.272437] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.278321] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.284068] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.289942] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.295752] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.301516] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.307405] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.313148] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.319026] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.324837] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.330596] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.336489] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.342229] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.348111] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.353860] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.359732] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.365543] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.371308] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.377195] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.382940] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.388817] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.394628] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.400389] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.406280] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.412019] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.417901] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.423652] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.429522] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.435333] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.441099] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.446985] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.452731] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.458607] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.464418] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.470180] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.476070] ath10k_pci 0000:01:00.0: No VIF found for vdev 0
[1482791.482344] ath10k_pci 0001:01:00.0: SWBA overrun on vdev 0, skipped old beacon
[1482791.488018] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
[1482791.495250] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
[1482791.501989] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
[1482797.502995] ath10k_pci 0000:01:00.0: 10.4 wmi init: vdevs: 16 peers: 48 tid: 96
[1482797.503021] ath10k_pci 0000:01:00.0: msdu-desc: 2500 skid: 32
[1482797.583427] ath10k_pci 0000:01:00.0: wmi print 'P 48/48 V 16 K 144 PH 176 T 186 msdu-desc: 2500 sw-crypt: 0 ct-sta: 0'
[1482797.584257] ath10k_pci 0000:01:00.0: wmi print 'free: 81784 iram: 23220 sram: 14440'
[1482797.936189] ath10k_pci 0000:01:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
[1482797.936483] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[1482797.958549] br-lan: port 3(wlan0) entered blocking state
[1482797.958578] br-lan: port 3(wlan0) entered disabled state
[1482797.963168] device wlan0 entered promiscuous mode
[1482858.961393] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[1482858.961703] br-lan: port 3(wlan0) entered blocking state
[1482858.966949] br-lan: port 3(wlan0) entered forwarding state
Have you tried installing 19.07.3 on top of the latest Archer C7 v5 OEM firmware (1.015)?
1 Like
the GitHub notification for the release only today out. This forum topic was much before. Why?
We don't use github releases (we already have enough channels), it was an experiment that was then cleaned up.
3 Likes