Personal token deployments
Personal tokens are no longer the supported way to authenticate Zephyr deployments from CI/CD pipelines.
Personal tokens still exist for user-scoped access where supported, but deployment authentication is moving to CI tokens. CI tokens are organization-scoped credentials designed for build pipelines and use the ZE_CI_TOKEN environment variable.
Deployment authentication is changing
Do not add ZE_SECRET_TOKEN to new deployment pipelines. Existing deployment pipelines that use personal tokens should migrate to CI tokens.
What to use instead
Use CI tokens for deployments from GitHub Actions, GitLab CI/CD, and other build pipelines.
Follow the deployment auth migration guide to replace ZE_SECRET_TOKEN with ZE_CI_TOKEN.
What changes for personal tokens
- Personal tokens are not being removed.
- Personal-token deployment authentication is going away.
- Existing deployment jobs should stop using
ZE_SECRET_TOKEN. - User-scoped token use outside deployments should continue only where the product supports it.