1. 21 Aug, 2019 1 commit
  2. 20 Aug, 2019 1 commit
  3. 30 Jul, 2019 1 commit
  4. 02 Jul, 2019 1 commit
  5. 28 Jun, 2019 1 commit
  6. 16 May, 2019 1 commit
  7. 07 May, 2019 1 commit
  8. 25 Apr, 2019 1 commit
  9. 08 Apr, 2019 1 commit
  10. 20 Mar, 2019 1 commit
  11. 09 Mar, 2019 1 commit
  12. 06 Mar, 2019 1 commit
  13. 21 Feb, 2019 1 commit
  14. 29 Jan, 2019 1 commit
  15. 26 Jan, 2019 1 commit
  16. 15 Nov, 2018 1 commit
  17. 14 Nov, 2018 1 commit
  18. 13 Nov, 2018 1 commit
  19. 11 Nov, 2018 1 commit
  20. 07 Nov, 2018 1 commit
  21. 30 Oct, 2018 2 commits
  22. 26 Oct, 2018 1 commit
  23. 05 Oct, 2018 1 commit
  24. 04 Oct, 2018 1 commit
  25. 01 Oct, 2018 1 commit
  26. 12 Sep, 2018 1 commit
  27. 30 Aug, 2018 1 commit
    • Greg Spencer's avatar
      Makes switching channels remove version freshness stamp. (#21182) · 7cebaac9
      Greg Spencer authored
      When switching between channels, we were leaving around the version freshness stamp file (bin/cache/flutter_version_check.stamp), which meant that the flutter tool would read from that file to see what the cached date of the most recent commit to the current channel (branch) was. The problem was that since the file was created while on the previous channel, the cached date was for the wrong channel, so if you switch from master to beta, flutter would think that the channel was out of date, and a new version was available, at least for three days after the first time it checked (after three days since the last time the freshness was checked, the cached date would get updated).
      
      This PR modifies the channel command to remove that stamp file whenever the user switches channels, so that the cached date will be from the right channel when it is recreated.
      
      Fixes #21134
      7cebaac9
  28. 02 Aug, 2018 1 commit
  29. 27 Jul, 2018 1 commit
  30. 23 Jul, 2018 1 commit
  31. 20 Jul, 2018 1 commit
  32. 16 Jul, 2018 2 commits
  33. 09 Jul, 2018 1 commit
  34. 27 Jun, 2018 1 commit
    • Danny Tuppeny's avatar
      Improve update checking (#18193) · e616c6ce
      Danny Tuppeny authored
      * Improve update checking
      
      This change emables pinging the server to check for updates regardless of whether the local version is "out of date". The server code already has a 7-day cache so the result is that we can now ping the server once every 7 days instead of waiting for the local install to be 4 weeks out of date before pinging.
      
      The original 4 week period is still used for when we'll start warning the user they're out of date if we could not confirm with the server whether there's a new version.
      
      * Improve message when we know there's a new version available
      
      * Fix bnullable bool checks
      
      * Switch nullable bool to enum
      
      * Fix casing of enum values
      
      * Remove stale comment
      
      The names are now descriptive so doesn't need additional explanation.
      
      * Improve name of function
      
      * Remove note:
      
      * Rename kPauseToLetUserReadTheMessage -> timeToPauseToLetUserReadTheMessage
      
      * Change kVersionAgeConsideredUpToDate to 5 weeks from 4
      
      * Inline the isNewerFrameworkVersionAvailable check
      
      * Fix indenting (?)
      
      * Fix more indenting
      
      * Rename function to be clearer it's getting the commit date
      
      * Formating tweaks
      
      * Update stamp when connection failed, and reduce time before we'll try again
      
      Previously we would hit the server on every command if we thought we might be out of date and we never successfully connected (eg. if you're offline). This makes the stamp update even when there's a conneciton failure so that this won't happen, but reduces the time till we check again from 7 days to 3 days to compensate a little in case it was a one-off.
      
      https://github.com/flutter/flutter/pull/18193#issuecomment-399222269
      
      * Fix comment
      
      * Don't perform update checks if not on an official channel
      e616c6ce
  35. 20 Jun, 2018 1 commit
  36. 05 Jun, 2018 1 commit
  37. 01 Jun, 2018 1 commit
  38. 18 May, 2018 1 commit