From 15ca4ac286b9b40d03f3b63c92cc1373728f4195 Mon Sep 17 00:00:00 2001 From: vitalragaz Date: Tue, 22 Sep 2026 17:21:29 +0000 Subject: [PATCH] chore: route public contact addresses to developers@ and security@speechify.ai --- LICENSE | 2 +- README.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/LICENSE b/LICENSE index cdf8634..4128628 100644 --- a/LICENSE +++ b/LICENSE @@ -1,6 +1,6 @@ MIT License -Copyright (c) 2026 SpeechifyAI (https://speechify.ai) +Copyright (c) 2026 SpeechifyAI (https://speechify.ai) Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal diff --git a/README.md b/README.md index db4a786..9950537 100644 --- a/README.md +++ b/README.md @@ -274,7 +274,7 @@ Publishing is tokenless. There are no repository or organization secrets in the - Authentication is npm [trusted publishing](https://docs.npmjs.com/trusted-publishers) over GitHub Actions OIDC (`id-token: write`). The trust is configured on npmjs.com for `@speechify/cli` and points at this repository and the `release-please.yml` workflow. Viewing or changing it needs an npm maintainer of the package (package Settings, Trusted Publisher). - npm allows one trusted publisher per package, so [`manual-publish.yml`](.github/workflows/manual-publish.yml) can only publish if that trust is re-pointed at it first. Dispatched with `dry_run` on (the default) it checks out a tag, builds, asserts the version and packs without contacting the registry, which is the way to prove the release path still works. -Maintainer contact: `devrel@speechify.com`. +Maintainer contact: `developers@speechify.ai`. Security reports: `security@speechify.ai`. ## Architecture