chore: update repository templates to ory/meta@c6bd2e0

Author: ory-bot

.github/ISSUE_TEMPLATE/BUG-REPORT.yml

@@ -25,10 +25,10 @@ body:
             Guidelines](https://github.com/ory/cli/blob/master/CONTRIBUTING.md)."
           required: true
         - label:
-            "I have joined the [Ory Community Slack](https://slack.ory.sh)."
+            "I have joined the [Ory Community Slack](https://slack.ory.com)."
         - label:
             "I am signed up to the [Ory Security Patch
-            Newsletter](https://www.ory.sh/l/sign-up-newsletter)."
+            Newsletter](https://www.ory.com/l/sign-up-newsletter)."
     id: checklist
     type: checkboxes
   - attributes:

.github/ISSUE_TEMPLATE/DESIGN-DOC.yml

@@ -36,10 +36,10 @@ body:
             Guidelines](https://github.com/ory/cli/blob/master/CONTRIBUTING.md)."
           required: true
         - label:
-            "I have joined the [Ory Community Slack](https://slack.ory.sh)."
+            "I have joined the [Ory Community Slack](https://slack.ory.com)."
         - label:
             "I am signed up to the [Ory Security Patch
-            Newsletter](https://www.ory.sh/l/sign-up-newsletter)."
+            Newsletter](https://www.ory.com/l/sign-up-newsletter)."
     id: checklist
     type: checkboxes
   - attributes:

.github/ISSUE_TEMPLATE/FEATURE-REQUEST.yml

@@ -29,10 +29,10 @@ body:
             Guidelines](https://github.com/ory/cli/blob/master/CONTRIBUTING.md)."
           required: true
         - label:
-            "I have joined the [Ory Community Slack](https://slack.ory.sh)."
+            "I have joined the [Ory Community Slack](https://slack.ory.com)."
         - label:
             "I am signed up to the [Ory Security Patch
-            Newsletter](https://www.ory.sh/l/sign-up-newsletter)."
+            Newsletter](https://www.ory.com/l/sign-up-newsletter)."
     id: checklist
     type: checkboxes
   - attributes:

.github/ISSUE_TEMPLATE/config.yml

@@ -9,6 +9,6 @@ contact_links:
       Please ask and answer questions here, show your implementations and
       discuss ideas.
   - name: Ory Chat
-    url: https://www.ory.sh/chat
+    url: https://www.ory.com/chat
     about:
       Hang out with other Ory community members to ask and answer questions.

.github/pull_request_template.md

@@ -24,7 +24,7 @@ Pull requests introducing new features, which do not have a design document link
 get merged.
 
 You can discuss changes with maintainers either in the Github Discussions in this repository or
-join the [Ory Chat](https://www.ory.sh/chat).
+join the [Ory Chat](https://www.ory.com/chat).
 -->
 
 ## Checklist
@@ -42,7 +42,7 @@ them, don't hesitate to ask. We're here to help! This is simply a reminder of wh
 - [ ] I confirm that this pull request does not address a security
       vulnerability. If this pull request addresses a security vulnerability, I
       confirm that I got approval (please contact
-      [security@ory.sh](mailto:security@ory.sh)) from the maintainers to push
+      [security@ory.com](mailto:security@ory.com)) from the maintainers to push
       the changes.
 - [ ] I have added tests that prove my fix is effective or that my feature
       works.

CODE_OF_CONDUCT.md

@@ -47,7 +47,7 @@ individual problems. If Ory open source software is used in production in a
 for-profit company or enterprise environment, we mandate a paid support contract
 where Ory is obligated under their service level agreements (SLAs) to offer a
 defined level of availability and responsibility. For more information about
-paid support please contact us at sales@ory.sh.
+paid support please contact us at sales@ory.com.
 
 ## Enforcement Responsibilities
 
@@ -73,7 +73,7 @@ representative at an online or offline event.
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
 reported to the community leaders responsible for enforcement at
-[office@ory.sh](mailto:office@ory.sh). All complaints will be reviewed and
+[office@ory.com](mailto:office@ory.com). All complaints will be reviewed and
 investigated promptly and fairly.
 
 All community leaders are obligated to respect the privacy and security of the

CONTRIBUTING.md

@@ -24,7 +24,7 @@
 
 _Please note_: We take Ory CLI's security and our users' trust very seriously.
 If you believe you have found a security issue in Ory CLI, please disclose it by
-contacting us at security@ory.sh.
+contacting us at security@ory.com.
 
 There are many ways in which you can contribute. The goal of this document is to
 provide a high-level overview of how you can get involved in Ory.
@@ -42,7 +42,7 @@ That said, if you want to ensure that a pull request is likely to be merged,
 talk to us! You can find out our thoughts and ensure that your contribution
 won't clash with Ory CLI's direction. A great way to do this is via
 [Ory CLI Discussions](https://github.com/orgs/ory/discussions) or the
-[Ory Chat](https://www.ory.sh/chat).
+[Ory Chat](https://www.ory.com/chat).
 
 ## FAQ
 
@@ -63,7 +63,7 @@ won't clash with Ory CLI's direction. A great way to do this is via
   Ory have [a Contributors License Agreement?](https://cla-assistant.io/ory/cli)
 
 - I would like updates about new versions of Ory CLI.
-  [How are new releases announced?](https://www.ory.sh/l/sign-up-newsletter)
+  [How are new releases announced?](https://www.ory.com/l/sign-up-newsletter)
 
 ## How can I contribute?
 
@@ -105,7 +105,7 @@ to help out:
 
 ## Communication
 
-We use [Slack](https://www.ory.sh/chat). You are welcome to drop in and ask
+We use [Slack](https://www.ory.com/chat). You are welcome to drop in and ask
 questions, discuss bugs and feature requests, talk to other users of Ory, etc.
 
 Check out [Ory CLI Discussions](https://github.com/orgs/ory/discussions). This
@@ -114,7 +114,7 @@ similar data.
 
 You can also join our community calls if you want to speak to the Ory team
 directly or ask some questions. You can find more info and participate in
-[Slack](https://www.ory.sh/chat) in the #community-call channel.
+[Slack](https://www.ory.com/chat) in the #community-call channel.
 
 If you want to receive regular notifications about updates to Ory CLI, consider
 joining the mailing list. We will _only_ send you vital information on the
@@ -136,7 +136,7 @@ to add your example or Ory-related project to the awesome-ory README.
 ## Contribute code
 
 Unless you are fixing a known bug, we **strongly** recommend discussing it with
-the core team via a GitHub issue or [in our chat](https://www.ory.sh/chat)
+the core team via a GitHub issue or [in our chat](https://www.ory.com/chat)
 before getting started to ensure your work is consistent with Ory CLI's roadmap
 and architecture.
 
@@ -205,7 +205,7 @@ instructions please head over to the Ory Documentation
 ## Disclosing vulnerabilities
 
 Please disclose vulnerabilities exclusively to
-[security@ory.sh](mailto:security@ory.sh). Do not use GitHub issues.
+[security@ory.com](mailto:security@ory.com). Do not use GitHub issues.
 
 ## Code style
 
@@ -247,4 +247,4 @@ community a safe place for you and we've got your back.
 
 We welcome discussion about creating a welcoming, safe, and productive
 environment for the community. If you have any questions, feedback, or concerns
-[please let us know](https://www.ory.sh/chat).
+[please let us know](https://www.ory.com/chat).

SECURITY.md

@@ -7,7 +7,7 @@ This policy outlines Ory's security commitments and practices for users across
 different licensing and deployment models.
 
 To learn more about Ory's security service level agreements (SLAs) and
-processes, please [contact us](https://www.ory.sh/contact/).
+processes, please [contact us](https://www.ory.com/contact/).
 
 ## Ory Network Users
 
@@ -53,4 +53,4 @@ processes, please [contact us](https://www.ory.sh/contact/).
 ## Reporting a Vulnerability
 
 For details on how to report security vulnerabilities, visit our
-[security policy documentation](https://www.ory.sh/docs/ecosystem/security).
+[security policy documentation](https://www.ory.com/docs/ecosystem/security).