From ca5f13d0e39f069a49861a1a060fed2eac6f6e5f Mon Sep 17 00:00:00 2001 From: Brad Warren Date: Thu, 9 Feb 2023 18:55:29 -0800 Subject: [PATCH] update snapcraft credentials --- .azure-pipelines/templates/jobs/snap-deploy-job.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.azure-pipelines/templates/jobs/snap-deploy-job.yml b/.azure-pipelines/templates/jobs/snap-deploy-job.yml index d1d709cb9..f4bc8eb00 100644 --- a/.azure-pipelines/templates/jobs/snap-deploy-job.yml +++ b/.azure-pipelines/templates/jobs/snap-deploy-job.yml @@ -19,7 +19,7 @@ jobs: # credential file was created by running: # # snapcraft logout - # snapcraft export-login --channels=candidate,beta,edge snapcraft.cfg + # snapcraft export-login --channels=beta,edge snapcraft.cfg # (provide the shared snapcraft credentials when prompted) # # Then the file was added as a secure file in Azure pipelines @@ -30,7 +30,7 @@ jobs: # https://docs.microsoft.com/en-us/azure/devops/pipelines/library/secure-files?view=azure-devops#q-how-do-i-authorize-a-secure-file-for-use-in-a-specific-pipeline. # # This file has a maximum lifetime of one year and the current file will - # expire on 2023-09-06. The file will need to be updated before then to + # expire on 2024-02-10. The file will need to be updated before then to # prevent automated deploys from breaking. # # Revoking these credentials can be done by changing the password of the