Change Details

By default, we should assume HTML pages are going to have information updated regularly (most notably, new release versions), especially as we apply more automation. This fixes an issue where a user who recently looked at the homepage or releases page will see the old version when revisiting the site after a new release becomes available. Pages under `/doc/` are not affected by this change and may be cached, since many of these pages are versioned and unlikely to change.

By default, we should assume HTML pages are going to have information updated regularly (most notably, new release versions), especially as we apply more automation. This fixes an issue where a user who recently looked at the homepage or releases page will see the old version when revisiting the site after a new release becomes available. CSS/JS and other assets are unaffected by this change. Pages under `/doc/` are not affected by this change and may be cached, since many of these pages are versioned and unlikely to change.

By default, we should assume HTML pages are going to have information updated regularly (most notably, new release versions), especially as we apply more automation. This fixes an issue where a user who recently looked at the homepage or releases page will see the old version when revisiting the site after a new release becomes available. CSS/JS and other assets are unaffected by this change. Pages under `/doc/` are not affected by this change and may be cached, since many of these pages are versioned and unlikely to change.