Обсуждение: Re: pgweb commit: 2023-05-11 update release
> On 11 May 2023, at 15:07, Jonathan S. Katz <jonathan.katz@excoventures.com> wrote: > > 2023-05-11 update release > > Branch > ------ > master > > Details > ------- > https://git.postgresql.org/gitweb?p=pgweb.git;a=commitdiff;h=b2fc8b51528f9887f84a42bca03a20e32bf9430b > > Modified Files > -------------- > templates/index.html | 44 ++++++++++++++++++++++------------ > templates/pages/developer/roadmap.html | 2 +- > templates/pages/include/topbar.html | 4 ++-- > 3 files changed, 32 insertions(+), 18 deletions(-) + This release fixes two security vulnerabilities over 80 bugs reported Should this have been "and fixes over"? + are running PostgreSQL 11 in a production environment, we suggest that + you make pgrade to a newer, supported version of PostgreSQL. Please "..that you upgrade to a.." -- Daniel Gustafsson
(dropping other email) On 5/11/23 9:09 AM, Daniel Gustafsson wrote: > + This release fixes two security vulnerabilities over 80 bugs reported > Should this have been "and fixes over"? > > + are running PostgreSQL 11 in a production environment, we suggest that > + you make pgrade to a newer, supported version of PostgreSQL. Please > "..that you upgrade to a.." Ugh, I missed both. I had some issues with my new code editor and missed during review. Fixing now. Jonathan
Вложения
On 5/11/23 9:33 AM, Jonathan S. Katz wrote: > (dropping other email) > > On 5/11/23 9:09 AM, Daniel Gustafsson wrote: > >> + This release fixes two security vulnerabilities over 80 >> bugs reported >> Should this have been "and fixes over"? >> >> + are running PostgreSQL 11 in a production environment, we >> suggest that >> + you make pgrade to a newer, supported version of >> PostgreSQL. Please >> "..that you upgrade to a.." > > Ugh, I missed both. I had some issues with my new code editor and missed > during review. Fixing now. Fixed in 1600eb55 and the announcement on the website. Interestingly, the announcement did not have the typo in the EOL section. Thanks, Jonathan