chore: update version to 1.6.2

This commit is contained in:
Linus Rath
2026-05-06 20:07:36 +02:00
parent 91cf125a5d
commit 178922323d
30 changed files with 89 additions and 43 deletions
+1 -1
View File
@@ -43,7 +43,7 @@ export async function GET() {
/**
* POST /api/admin/version
* { action: 'check-now' } force a fresh upstream fetch.
* { action: 'check-now' } - force a fresh upstream fetch.
*/
export async function POST(req: NextRequest) {
try {
+1 -1
View File
@@ -44,7 +44,7 @@ export async function POST(request: NextRequest) {
// caller cannot point this route at internal hosts. We accept the global
// `jmapServerUrl` and any entry from `jmapServers`. When neither matches,
// we fall back to the request URL only if `allowCustomJmapEndpoint` is on
// and even then the URL must resolve to a public address.
// - and even then the URL must resolve to a public address.
await configManager.ensureLoaded();
const configuredServerUrl =
configManager.get<string>('jmapServerUrl', '') ||
+1 -1
View File
@@ -91,7 +91,7 @@ export async function POST(request: NextRequest) {
// Pin the upstream URL to a configured JMAP server. The list of allowed
// servers is `jmapServerUrl` plus any entry from `jmapServers`. Only when
// no server is configured (and the deployment explicitly allows custom
// JMAP endpoints) do we fall back to the user-supplied URL and even then
// JMAP endpoints) do we fall back to the user-supplied URL - and even then
// it must resolve to a public address.
await configManager.ensureLoaded();
const configuredServerUrl =
+1 -1
View File
@@ -163,7 +163,7 @@ export async function GET(request: NextRequest) {
},
});
} catch (error) {
// `fetch failed` from undici is too generic to debug the real reason
// `fetch failed` from undici is too generic to debug - the real reason
// (ENOTFOUND, ECONNREFUSED, TLS error, …) is on `error.cause`.
const err = error as Error & { cause?: { code?: string; message?: string } };
logger.error('push preview failed', {