Timezone Support for Scheduled Workflows

GitHub Actions now allows developers to specify IANA timezones directly in workflow schedules. Instead of being locked to UTC, you can now add a timezone field alongside your cron expression. For example, you can configure a workflow to run at 2 PM Eastern Time by specifying timezone: "America/New_York" alongside your cron schedule. This eliminates the need for manual UTC offset calculations and makes scheduled workflows more intuitive to manage across distributed teams.

Environments Without Auto-Deployment

The second major update allows developers to use environments purely for secrets and variables management without automatically creating deployments. By configuring an environment with the deployment: false key, teams can leverage GitHub's environment features while avoiding unnecessary deployment records. This is particularly useful for workflows that need environment-scoped secrets but don't actually deploy infrastructure.

Important limitation: Custom deployment protection rules are not compatible with deployment: false. If your organization uses custom protection rules, environments will continue to require auto-deployment.

How to Use These Features

• For timezone support: Update your workflow YAML with the timezone field in your on.schedule section
• For environment-only mode: Set deployment: false in your environment configuration via the GitHub UI or API

Both features are immediately available to all GitHub Actions users. Refer to the GitHub Actions documentation for detailed configuration examples and additional context.