atom/atom.io

atom.io incorrectly showing 1.39 available

Closed this issue · 7 comments

hermidalc commented

Edit by @rsese: http://atom.io says 1.39.0 is available for download, but the releases you get are for 1.38.

rsese commented

Thanks for the heads up @hermidalc - 1.39.0 hasn't been released yet so atom.io is showing the wrong release version details /cc @jasonrudolph

  • 👍1
jasonrudolph commented

Thanks for the heads up. This should be fixed now.

Screen Shot 2019-07-20 at 7 45 00 AM

  • 👍1
  • ❤️1
hermidalc commented

Tell me I'm crazy... but website it showing 1.39 again yet the downloadable Linux rpm is still 1.38.2

$ sudo dnf install -y Downloads/atom.x86_64.rpm 
Fedora Modular 30 - x86_64                                                                                            247 kB/s |  18 kB     00:00    
Fedora Modular 30 - x86_64 - Updates                                                                                  184 kB/s |  17 kB     00:00    
Fedora 30 - x86_64 - Updates                                                                                           39 kB/s |  17 kB     00:00    
Fedora 30 - x86_64                                                                                                     47 kB/s |  18 kB     00:00    
Package atom-1.38.2-0.1.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!
Arcanemagus commented

As you can see from the releases page v1.38.2 is still the current stable build, looks like the website is jumping the gun a bit again 😆.

  • 👍1
jasonrudolph commented

As you can see from the releases page v1.38.2 is still the current stable build, looks like the website is jumping the gun a bit again 😆.

Can you tell that we were excited to ship v1.39.0? 😂

It's out for real now, so atom.io is now telling the truth about the latest version. 😅 With that in mind, I think we can close this issue now.

  • 😄2
Aerijo commented

@jasonrudolph Stable is still 1.39.1

image

jasonrudolph commented

Thanks for reopening this issue, @Aerijo. 🙇

I think I've tracked down the root cause. atom.io receives a webhook payload for release events, but atom.io wasn't distinguishing between a draft release and a published release. We've rolled out a fix to atom.io to only update the Atom version when a new stable release is published. 😅

  • ❤️2