905f0c7451
full 2019.06.23.05 beta release
2019-06-23 23:28:28 -04:00
84a2916a25
clarify hardened_malloc fix in 2019.06.23.05
2019-06-23 23:28:20 -04:00
9f716559cf
2019.06.23.05 release for sargo/bonito
2019-06-23 18:30:39 -04:00
b6d3ec4d5a
2019.06.23.05 release notes
2019-06-23 18:17:55 -04:00
e09bfdf7aa
move fonts to dedicated subdirectory
2019-06-18 23:39:06 -04:00
171b0328fb
2019.06.14.02 release fully pushed out
2019-06-14 17:24:30 -04:00
ae3633cd11
2019.06.14.02 release
2019-06-14 10:45:31 -04:00
f550d5d865
yet another experimental bonito / sargo release
2019-06-14 01:06:36 -04:00
8f794c8eae
new experimental bonito / sargo release
2019-06-13 20:23:01 -04:00
ea197efbbd
initial support for the Pixel 3a and Pixel 3a XL
2019-06-13 15:32:05 -04:00
217ed817d4
set up first experimental release for bonito/sargo
2019-06-13 14:02:29 -04:00
60902ba216
releases: add hidden sections for bonito and sargo
2019-06-13 13:51:15 -04:00
f424932ea5
drop unnecessary favicon query string for compat
...
Skype appears to be unable to handle this and tries /favicon.ico%3F0
which triggers a 404 errors. The user agent is the following:
Mozilla/5.0 (Windows NT 6.1; WOW64) SkypeUriPreview Preview/0.5
2019-06-12 13:58:44 -04:00
fe550c7556
seamlessupdate.app -> releases.grapheneos.org
2019-06-09 09:20:05 -04:00
9555670ea4
consistent clarification for Chromium changes
2019-06-06 12:04:45 -04:00
af38beedef
regenerate stable-channel section
2019-06-04 08:27:18 -04:00
105ea5cb82
regenerate beta-channel section
2019-06-04 02:02:53 -04:00
84de593b58
remove obsolete header text
2019-06-03 22:32:54 -04:00
c8e3beeb10
add 2019.06.03.18 release notes
2019-06-03 20:04:51 -04:00
796aa5b9bc
specify tag to use for other devices
2019-06-03 14:39:11 -04:00
a7848665f1
adjust approach to header links
2019-06-03 12:27:06 -04:00
4504a04635
add twitter:site and twitter:creator metadata
...
This isn't currently displayed in the Twitter cards despite it being in
the official documentation for cards, but other crawlers are definitely
using this metadata.
2019-06-02 02:17:34 -04:00
ddf1e18edb
use standard mime type for favicon
2019-05-30 21:17:42 -04:00
72d417c8dd
work around Microsoft Edge TileColor bug
2019-05-30 15:33:23 -04:00
e0a6799fd6
add mask icon for Safari
2019-05-29 06:27:27 -04:00
61b46ac016
add explicit rel="icon" link for favicon.ico
2019-05-26 04:13:44 -04:00
7421ee5043
regenerate static stable channel section
2019-05-19 20:51:23 -04:00
c4c6535686
regenerate static beta channel section
2019-05-19 15:47:25 -04:00
49c36eb766
changelog for 2019.05.18.20
2019-05-19 13:56:29 -04:00
04ed24bc9d
add padding between footer links
2019-05-16 16:27:56 -04:00
746eed0a6a
use a list for footer links
2019-05-16 15:57:00 -04:00
c988573fa9
machine readable JavaScript license per request
2019-05-12 19:26:01 -04:00
770f917ff2
update Roboto woff2 files
2019-05-11 18:39:49 -04:00
af851260ca
mark device sections as such
2019-05-11 12:48:45 -04:00
fbfd38472d
remove leftover id tag
2019-05-11 12:31:19 -04:00
01f5ee99a8
add pre-generated releases template
2019-05-11 12:24:26 -04:00
0622c652e5
increment CSS version
2019-05-10 17:54:02 -04:00
a229e9e917
remove code for handling missing tags
2019-05-10 17:45:43 -04:00
2ed2ba8bf5
replace line breaks with lists for releases page
2019-05-10 17:29:40 -04:00
2ba653ca55
update releases links instead of replacing
2019-05-10 17:16:37 -04:00
f293459943
add missing changelog link
2019-05-09 18:29:51 -04:00
947599ca50
update link indexes for releases script
2019-05-09 18:18:09 -04:00
525ef01b27
add header links for each device-channel header
2019-05-09 18:00:20 -04:00
2427ea0db6
reuse existing template for releases
2019-05-09 17:55:55 -04:00
724e1c200e
add header links to the releases page
2019-05-09 16:24:29 -04:00
d95a7fe1d5
add more header ids for usage in links
2019-05-09 16:17:33 -04:00
cd5f1a8675
add changelog for 2019.05.08.15
2019-05-08 18:21:29 -04:00
f3b13c8357
replace logo image
2019-05-08 14:48:54 -04:00
36a3158244
replace opengraph image
2019-05-08 14:45:13 -04:00
a51abed84e
add og:image:width and og:image:height
...
These are considered a best practice by Facebook and result in the image
appearing properly when shared for the first time. It will also be quite
useful when there are multiple images suited to different sizes.
2019-05-08 13:20:47 -04:00
Daniel Micay