chore: Change repo URL to the new location

Author: sthulb

.github/CODEOWNERS

@@ -1,3 +1,3 @@
 # https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners
 
-* @awslabs/aws-lambda-powertools-typescript
+* @aws-powertools/lambda-typescript

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -6,7 +6,7 @@ body:
   - type: markdown
     attributes:
       value: |
-        Thank you for submitting a bug report. Before you start, make sure that [the bug hasn't been reported already](https://github.com/awslabs/aws-lambda-powertools-typescript/issues).
+        Thank you for submitting a bug report. Before you start, make sure that [the bug hasn't been reported already](https://github.com/aws-powertools/lambda-typescript/issues).
         
         Please add as much information as possible to help us reproduce, and remove any potential sensitive data.
   - type: textarea

.github/ISSUE_TEMPLATE/config.yml

@@ -1,7 +1,7 @@
 blank_issues_enabled: false
 contact_links:
   - name: Ask a question
-    url: https://github.com/awslabs/aws-lambda-powertools-typescript/discussions/new
+    url: https://github.com/aws-powertools/lambda-typescript/discussions/new
     about: Ask a general question about Lambda Powertools
   - name: Join Community Discord Server
     url: https://discord.gg/B8zZKbbyET

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,6 +1,6 @@
 <!--- 
 Instructions:
-1. Make sure you follow our Contributing Guidelines: https://github.com/awslabs/aws-lambda-powertools-typescript/blob/main/CONTRIBUTING.md
+1. Make sure you follow our Contributing Guidelines: https://github.com/aws-powertools/lambda-typescript/blob/main/CONTRIBUTING.md
 2. Please follow the template, and do not remove any section/item. If something is not applicable leave it empty, but leave it in the PR. 
 3. -->
 
@@ -34,7 +34,7 @@ Note: If no issue is present the PR might get blocked and not be reviewed.
 - [ ] I have made corresponding changes to the *documentation*
 - [ ] My changes generate *no new warnings*
 - [ ] I have *added tests* that prove my change is effective and works
-- [ ] The PR title follows the [conventional commit semantics](https://github.com/awslabs/aws-lambda-powertools-typescript/blob/main/.github/semantic.yml#L2)
+- [ ] The PR title follows the [conventional commit semantics](https://github.com/aws-powertools/lambda-typescript/blob/main/.github/semantic.yml#L2)
 
 ### Breaking change checklist
 

.github/boring-cyborg.yml

@@ -158,7 +158,7 @@ labelPRBasedOnFilePath:
 
 ##### Greetings ########################################################################################################
 firstPRWelcomeComment: >
-  Thanks a lot for your first contribution! Please check out our [contributing guidelines](https://github.com/awslabs/aws-lambda-powertools-typescript/blob/chore/pr_automation/CONTRIBUTING.md) and don't hesitate to ask whatever you need.
+  Thanks a lot for your first contribution! Please check out our [contributing guidelines](https://github.com/aws-powertools/lambda-typescript/blob/chore/pr_automation/CONTRIBUTING.md) and don't hesitate to ask whatever you need.
 
   In the meantime, check out the #typescript channel on our AWS Lambda Powertools Discord: [Invite link](https://discord.gg/B8zZKbbyET)
 

.github/scripts/constants.js

@@ -31,7 +31,7 @@ module.exports = Object.freeze({
   "LABEL_RELEASED": "status/completed",
 
   /** @type {string} */
-  "HANDLE_MAINTAINERS_TEAM": "@awslabs/aws-lambda-powertools-typescript",
+  "HANDLE_MAINTAINERS_TEAM": "@aws-powertools/lambda-typescript",
 
   /** @type {string[]} */
   "IGNORE_AUTHORS": ["dependabot[bot]"],

.github/workflows/dispatch_analytics.yml

@@ -23,7 +23,7 @@ permissions:
 
 jobs:
   dispatch_token:
-    if: github.repository == 'awslabs/aws-lambda-powertools-typescript'
+    if: github.repository == 'aws-powertools/lambda-typescript'
     concurrency:
       group: analytics
     runs-on: ubuntu-latest

.github/workflows/reusable-publish-docs.yml

@@ -2,7 +2,7 @@ name: Reusable Publish docs
 
 env:
   BRANCH: main
-  ORIGIN: awslabs/aws-lambda-powertools-typescript
+  ORIGIN: aws-powertools/lambda-typescript
   VERSION: ""
 
 on:

.github/workflows/reusable_export_pr_details.yml

@@ -36,7 +36,7 @@ on:
 jobs:
   export_pr_details:
     # see https://github.com/awslabs/aws-lambda-powertools-python/issues/1349
-    if: inputs.workflow_origin == 'awslabs/aws-lambda-powertools-typescript'
+    if: inputs.workflow_origin == 'aws-powertools/lambda-typescript'
     runs-on: ubuntu-latest
     env:
       FILENAME: pr.txt

CHANGELOG.md

@@ -64,7 +64,7 @@ The following steps describe how to set up the AWS Lambda Powertools for TypeScr
 
 The alternative is to use a Cloud IDE like [Gitpod](https://www.gitpod.io/) or [GitHub CodeSpaces](https://github.com/features/codespaces) for your development. To quickly get up and running you can click one of these button to open a cloned version of this repo with all of the prerequisites and dependencies installed:
 
-[![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/#https://github.com/awslabs/aws-lambda-powertools-typescript)
+[![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/#https://github.com/aws-powertools/lambda-typescript)
 [![Open in GitHub Codespaces](https://github.com/codespaces/badge.svg)](https://github.com/codespaces/new?hide_repo_select=true&ref=main&repo=305501331)
 
 ### Setup
@@ -280,10 +280,10 @@ Contributions via pull requests are much appreciated.
 ### Step 1: Find something to work on
 
 If you want to contribute a specific feature or fix you have in mind, look at active [pull
-requests](https://github.com/awslabs/aws-lambda-powertools-typescript/pulls) to see if someone else is already working on it. If not, you can start designing your changes. 
+requests](https://github.com/aws-powertools/lambda-typescript/pulls) to see if someone else is already working on it. If not, you can start designing your changes. 
 
 On the other hand, if you are here looking for an issue to work on, check out our [backlog of
-issues](https://github.com/awslabs/aws-lambda-powertools-typescript/issues) and find something that piques your interest. Our project, by default, uses the default GitHub issue labels (enhancement/bug/help wanted/invalid/question/documentation), looking at any issue labeled as 'help wanted' or 'good-first-issue' is a great place to start.
+issues](https://github.com/aws-powertools/lambda-typescript/issues) and find something that piques your interest. Our project, by default, uses the default GitHub issue labels (enhancement/bug/help wanted/invalid/question/documentation), looking at any issue labeled as 'help wanted' or 'good-first-issue' is a great place to start.
 
 It's a good idea to keep the priority of issues in mind when deciding what to
 work on. If we have labelled an issue as `priority:medium` or `priority:low`, it means it's something we won't
@@ -295,7 +295,7 @@ You can start by checking the project's tenets [here](https://awslabs.github.io/
 
 We ask you to seek feedback and consensus on your proposed change by iterating on a design document. This is especially useful when you plan a big change or feature, or you want advice on what would be the best path forward.
 
-If you're picking up an existing issue, you can simply post your comment and discuss your proposed changes. If instead you're proposing a new feature, you can start by creating a new [RFC issue](https://github.com/awslabs/aws-lambda-powertools-typescript/issues/new?assignees=&labels=RFC%2C+triage&template=rfc.md&title=RFC%3A+) and discuss your proposed change with the maintainers.
+If you're picking up an existing issue, you can simply post your comment and discuss your proposed changes. If instead you're proposing a new feature, you can start by creating a new [RFC issue](https://github.com/aws-powertools/lambda-typescript/issues/new?assignees=&labels=RFC%2C+triage&template=rfc.md&title=RFC%3A+) and discuss your proposed change with the maintainers.
 
 This is a great way to get feedback on your proposed change and make sure that it is in line with the project's direction and community needs. You can start working on the change when you've gotten approved by at least one maintainer - we would hate for your time to be wasted.
 

CONTRIBUTING.md

@@ -133,7 +133,7 @@ Review pull requests regularly, comment, suggest, reject, merge and close. Accep
 
 PRs are [labeled](#labels) based on file changes and semantic title. Pay attention to whether labels reflect the current state of the PR and correct accordingly.
 
-Use and enforce [semantic versioning](https://semver.org/) pull request titles, as these will be used for [CHANGELOG](CHANGELOG.md) and [Release notes](https://github.com/awslabs/aws-lambda-powertools-typescript/releases) - make sure they communicate their intent at the human level.
+Use and enforce [semantic versioning](https://semver.org/) pull request titles, as these will be used for [CHANGELOG](CHANGELOG.md) and [Release notes](https://github.com/aws-powertools/lambda-typescript/releases) - make sure they communicate their intent at the human level.
 
 For issues linked to a PR, our automation should apply the `status/pending-release` label. Make sure the label is always applied when merging. [Upon release](#releasing-a-new-version), these issues will be notified which release version contains their change.
 
@@ -175,7 +175,7 @@ RFC is a collaborative process to help us get to the most optimal solution given
 
 Make sure you ask these questions in mind when reviewing:
 
-- Does it use our [RFC template](https://github.com/awslabs/aws-lambda-powertools-typescript/issues/new?assignees=&labels=RFC%2Ctriage&template=rfc.yml&title=RFC%3A+TITLE)?
+- Does it use our [RFC template](https://github.com/aws-powertools/lambda-typescript/issues/new?assignees=&labels=RFC%2Ctriage&template=rfc.yml&title=RFC%3A+TITLE)?
 - Does the match our [Tenets](https://awslabs.github.io/aws-lambda-powertools-typescript/latest/#tenets)?
 - Does the proposal address the use case? If so, is the recommended usage explicit?
 - Does it focus on the mechanics to solve the use case over fine-grained implementation details?
@@ -186,23 +186,23 @@ Make sure you ask these questions in mind when reviewing:
 
 When necessary, be upfront that the time to review, approve, and implement a RFC can vary - see [Contribution is stuck](#contribution-is-stuck). Some RFCs may be further updated after implementation, as certain areas become clearer.
 
-An example of a successful RFC: [#447](https://github.com/awslabs/aws-lambda-powertools-typescript/issues/447)
+An example of a successful RFC: [#447](https://github.com/aws-powertools/lambda-typescript/issues/447)
 
 ### Releasing a new version
 
 🚧 WIP 🚧
 
 #### Drafting release notes
 
-Visit the [Releases page](https://github.com/awslabs/aws-lambda-powertools-typescript/releases) and choose the edit pencil button.
+Visit the [Releases page](https://github.com/aws-powertools/lambda-typescript/releases) and choose the edit pencil button.
 
 Make sure the `tag` field reflects the new version you're releasing, the target branch field is set to `main`, and `release title` matches your tag e.g., `v1.4.1`.
 
 You'll notice we group all changes based on their [labels](#labels) like `type/feature`, `type/bug`, `type/documentation`, etc.
 
 **I spotted a typo or incorrect grouping - how do I fix it?**
 
-Edit the respective PR title and update their [labels](#labels). Then run the [Release Drafter workflow](https://github.com/awslabs/aws-lambda-powertools-typescript/actions/workflows/release-drafter.yml) to update the Draft release.
+Edit the respective PR title and update their [labels](#labels). Then run the [Release Drafter workflow](https://github.com/aws-powertools/lambda-typescript/actions/workflows/release-drafter.yml) to update the Draft release.
 
 **All looking good, what's next?**
 
@@ -218,17 +218,17 @@ These are some questions to keep in mind when drafting your first or future rele
 
 Once you're happy, hit `Publish release` 🎉🎉🎉.
 
-This will kick off the [Publish docs on release](https://github.com/awslabs/aws-lambda-powertools-typescript/blob/main/.github/workflows/publish-docs-on-release.yml) workflow and within a few minutes you should see the latest version in PyPi, and all issues labeled as `pending-release` will be closed and notified.
+This will kick off the [Publish docs on release](https://github.com/aws-powertools/lambda-typescript/blob/main/.github/workflows/publish-docs-on-release.yml) workflow and within a few minutes you should see the latest version in PyPi, and all issues labeled as `pending-release` will be closed and notified.
 
 ### Run end to end tests
 
-E2E tests should be ran before every merge to `main` or manually via [run-e2e-tests workflow](https://github.com/awslabs/aws-lambda-powertools-typescript/actions/workflows/run-e2e-tests.yml) before making a release.
+E2E tests should be ran before every merge to `main` or manually via [run-e2e-tests workflow](https://github.com/aws-powertools/lambda-typescript/actions/workflows/run-e2e-tests.yml) before making a release.
 
 To run locally, you need [AWS CDK CLI](https://docs.aws.amazon.com/cdk/v2/guide/getting_started.html#getting_started_prerequisites) and an [account bootstrapped](https://docs.aws.amazon.com/cdk/v2/guide/bootstrapping.html) (`cdk bootstrap`). With a default AWS CLI profile configured, or `AWS_PROFILE` environment variable set, run `npm run test:e2e -ws`.
 
 ### Releasing a documentation hotfix
 
-You can rebuild the latest documentation without a full release via this [GitHub Actions Workflow](https://github.com/awslabs/aws-lambda-powertools-typescript/blob/main/.github/workflows/publish-docs-on-release.yml). Choose `Run workflow`, keep `main` as the branch, and input the latest Powertools version available i.e. `v1.4.1`.
+You can rebuild the latest documentation without a full release via this [GitHub Actions Workflow](https://github.com/aws-powertools/lambda-typescript/blob/main/.github/workflows/publish-docs-on-release.yml). Choose `Run workflow`, keep `main` as the branch, and input the latest Powertools version available i.e. `v1.4.1`.
 
 This workflow will update both user guide and API documentation.
 
@@ -276,7 +276,7 @@ Note that issues marked as `need-response` will be automatically closed after 3
 
 ### Crediting contributions
 
-We credit all contributions as part of each [release note](https://github.com/awslabs/aws-lambda-powertools-typescript/releases) as an automated process. If you find contributors are missing from the release note you're producing, please add them manually.
+We credit all contributions as part of each [release note](https://github.com/aws-powertools/lambda-typescript/releases) as an automated process. If you find contributors are missing from the release note you're producing, please add them manually.
 
 ### Is that a bug?
 

MAINTAINERS.md

@@ -8,7 +8,7 @@ You can use the library in both TypeScript and JavaScript code bases.
 
 > Also available in [Python](https://github.com/awslabs/aws-lambda-powertools-python), [Java](https://github.com/awslabs/aws-lambda-powertools-java), and [.NET](https://awslabs.github.io/aws-lambda-powertools-dotnet/).
 
-**[Documentation](https://awslabs.github.io/aws-lambda-powertools-typescript/)** | **[npm](https://www.npmjs.com/org/aws-lambda-powertools)** | **[Roadmap](https://awslabs.github.io/aws-lambda-powertools-typescript/latest/roadmap)** | **[Examples](https://github.com/awslabs/aws-lambda-powertools-typescript/tree/main/examples)** | **[Serverless TypeScript Demo](https://github.com/aws-samples/serverless-typescript-demo)**
+**[Documentation](https://awslabs.github.io/aws-lambda-powertools-typescript/)** | **[npm](https://www.npmjs.com/org/aws-lambda-powertools)** | **[Roadmap](https://awslabs.github.io/aws-lambda-powertools-typescript/latest/roadmap)** | **[Examples](https://github.com/aws-powertools/lambda-typescript/tree/main/examples)** | **[Serverless TypeScript Demo](https://github.com/aws-samples/serverless-typescript-demo)**
 
 ## Table of contents <!-- omit in toc -->
 
@@ -75,8 +75,8 @@ Or refer to the installation guide of each utility:
 
 ### Examples
 
-* [CDK](https://github.com/awslabs/aws-lambda-powertools-typescript/tree/main/examples/cdk)
-* [SAM](https://github.com/awslabs/aws-lambda-powertools-typescript/tree/main/examples/sam)
+* [CDK](https://github.com/aws-powertools/lambda-typescript/tree/main/examples/cdk)
+* [SAM](https://github.com/aws-powertools/lambda-typescript/tree/main/examples/sam)
 
 ### Serverless TypeScript Demo application
 
@@ -85,12 +85,12 @@ You can find instructions on how to deploy and load test this application in the
 
 ## Contribute
 
-If you are interested in contributing to this project, please refer to our [Contributing Guidelines](https://github.com/awslabs/aws-lambda-powertools-typescript/blob/main/CONTRIBUTING.md).
+If you are interested in contributing to this project, please refer to our [Contributing Guidelines](https://github.com/aws-powertools/lambda-typescript/blob/main/CONTRIBUTING.md).
 
 ## Roadmap
 
 The roadmap of Powertools is driven by customers’ demand.  
-Help us prioritize upcoming functionalities or utilities by [upvoting existing RFCs and feature requests](https://github.com/awslabs/aws-lambda-powertools-typescript/issues), or [creating new ones](https://github.com/awslabs/aws-lambda-powertools-typescript/issues/new/choose), in this GitHub repository.
+Help us prioritize upcoming functionalities or utilities by [upvoting existing RFCs and feature requests](https://github.com/aws-powertools/lambda-typescript/issues), or [creating new ones](https://github.com/aws-powertools/lambda-typescript/issues/new/choose), in this GitHub repository.
 
 ## Connect
 
@@ -101,7 +101,7 @@ Help us prioritize upcoming functionalities or utilities by [upvoting existing R
 
 ### Becoming a reference customer
 
-Knowing which companies are using this library is important to help prioritize the project internally. If your company is using AWS Lambda Powertools for TypeScript, you can request to have your name and logo added to the README file by raising a [Support Lambda Powertools (become a reference)](https://github.com/awslabs/aws-lambda-powertools-typescript/issues/new?assignees=&labels=customer-reference&template=support_powertools.yml&title=%5BSupport+Lambda+Powertools%5D%3A+%3Cyour+organization+name%3E){target="_blank"} issue.
+Knowing which companies are using this library is important to help prioritize the project internally. If your company is using AWS Lambda Powertools for TypeScript, you can request to have your name and logo added to the README file by raising a [Support Lambda Powertools (become a reference)](https://github.com/aws-powertools/lambda-typescript/issues/new?assignees=&labels=customer-reference&template=support_powertools.yml&title=%5BSupport+Lambda+Powertools%5D%3A+%3Cyour+organization+name%3E){target="_blank"} issue.
 
 The following companies, among others, use Powertools:
 
@@ -127,4 +127,4 @@ Credits for the Lambda Powertools idea go to [DAZN](https://github.com/getndazn)
 
 ## License
 
-This library is licensed under the MIT-0 License. See the [LICENSE](https://github.com/awslabs/aws-lambda-powertools-typescript/blob/main/LICENSE) file.
+This library is licensed under the MIT-0 License. See the [LICENSE](https://github.com/aws-powertools/lambda-typescript/blob/main/LICENSE) file.

README.md

@@ -635,7 +635,7 @@ This is a Jest sample that provides the minimum information necessary for Logger
     ```
 
 !!! tip
-    If you don't want to declare your own dummy Lambda Context, you can use [`ContextExamples.helloworldContext`](https://github.com/awslabs/aws-lambda-powertools-typescript/blob/main/packages/commons/src/samples/resources/contexts/hello-world.ts#L3-L16) from [`@aws-lambda-powertools/commons`](https://www.npmjs.com/package/@aws-lambda-powertools/commons).
+    If you don't want to declare your own dummy Lambda Context, you can use [`ContextExamples.helloworldContext`](https://github.com/aws-powertools/lambda-typescript/blob/main/packages/commons/src/samples/resources/contexts/hello-world.ts#L3-L16) from [`@aws-lambda-powertools/commons`](https://www.npmjs.com/package/@aws-lambda-powertools/commons).
 
 ### Suppress logs with Jest