Skip to content

chore: route public contact addresses to developers@ and security@speechify.ai #25

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
vitalragaz merged 1 commit into from
Sep 25, 2026
Merged

chore: route public contact addresses to developers@ and security@speechify.ai #25

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion LICENSE
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
MIT License

Copyright (c) 2026 SpeechifyAI <devrel@speechify.com> (https://speechify.ai)
Copyright (c) 2026 SpeechifyAI <developers@speechify.ai> (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
Expand Down
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
Loading