Skip to content

Commit

Permalink
Update attestation-service.md (#1427)
Browse files Browse the repository at this point in the history
- replace broken google links
- replace broken security link
  • Loading branch information
GigaHierz committed Aug 22, 2024
1 parent 4bbcda8 commit 475a5dc
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/community/release-process/attestation-service.md
Original file line number Diff line number Diff line change
Expand Up @@ -73,7 +73,7 @@ Currently hosted core developer keys used for Attestation Service releases inclu

### Docker images

Docker images are built automatically with [Google Cloud Build](https://cloud.google.com/cloud-build) upon pushes to `master` and all release branches. Automated builds will be tagged in [Google Container Registry](https://cloud.google.com/container-registry) with the corresponding commit hash.
Docker images are built automatically with [Google Cloud Build](https://cloud.google.com/build) upon pushes to `master` and all release branches. Automated builds will be tagged in [Google Artifact Registry](https://cloud.google.com/artifact-registry) with the corresponding commit hash.

A signature should be produced over the image automatically built at the corresponding commit hash and included with the Github release.

Expand Down Expand Up @@ -145,4 +145,4 @@ If the issue is exploitable and mitigations are not readily available, a patch s

## Vulnerability Disclosure

Vulnerabilities in Attestation Service releases should be disclosed according to the [security policy](https://github.com/celo-org/celo-monorepo/blob/master/SECURITY.md).
Vulnerabilities in Attestation Service releases should be disclosed according to the [security policy](https://github.com/celo-org/celo-blockchain/blob/master/SECURITY.md).

0 comments on commit 475a5dc

Please sign in to comment.