fix: migrate to the website location

.github/workflows/publish-to-other-than-github.yaml

@@ -143,6 +143,6 @@ jobs:
       uses: peter-evans/repository-dispatch@28959ce8df70de7be546dd1250a005dd32156697 # v4.0.1
       with:
         token: ${{ steps.generate_token.outputs.token }}
-        repository: open-component-model/ocm-website
+        repository: open-component-model/open-component-model
         event-type: ocm-cli-release
         client-payload: '{"tag": "${{ env.RELEASE_VERSION }}"}'

README.md

@@ -162,7 +162,11 @@ More comprehensive examples can be taken from the [`components`](components) con
 
 ## GPG Public Key
 
-The authenticity of released packages that have been uploaded to public repositories can be verified using our GPG public key. You can find the current key in the file [OCM-RELEASES-PUBLIC-CURRENT.gpg](https://ocm.software/gpg/OCM-RELEASES-PUBLIC-CURRENT.gpg) on our website. You can find the old keys in the website github repository [here](https://github.com/open-component-model/ocm-website/tree/main/static/gpg).
+The authenticity of released packages that have been uploaded to public repositories can be verified using our GPG
+public key. You can find the current key in the file
+[OCM-RELEASES-PUBLIC-CURRENT.gpg](https://ocm.software/gpg/OCM-RELEASES-PUBLIC-CURRENT.gpg) on our website.
+You can find the old keys in the website github repository
+[here](https://github.com/open-component-model/open-component-model/tree/main/website/static/gpg).
 
 ## Contributing
 

RELEASE_PROCESS.md

@@ -279,7 +279,7 @@ In case of error you can try to [Manually retrigger the publishing of ocm-cli to
 
 ### ocm-website
 
-[Update the website](https://github.com/open-component-model/ocm-website/pulls).
+[Update the website](https://github.com/open-component-model/open-component-model/pulls).
 
 ### homebrew-tap