GitHub Actions: Late March 2026 updates

This month, GitHub Actions resolves some outstanding papercuts, including support for timezones in scheduled workflows and using environments without automatic deployments.

GitHub Actions now allows developers to use environments without auto-deployment

GitHub Actions now supports using environments in workflows without automatically creating a deployment. Many users have indicated that they want to be able to use the secrets and variables management capabilities of environments without creating additional deployments. If you configure an environment with the deployment: false key, you can access the environment but won’t create a new deployment. More information can be found in our docs on using environments without deployments.

Please note that if you are using a custom deployment protection rule, you will not be able to use the deployment: false key and using environments will require an auto-deploy.

GitHub Actions: Timezone support for scheduled workflows

You can now specify an IANA timezone on your cron schedules instead of being locked to UTC. Add a timezone field alongside your cron expression (e.g., timezone: "America/New_York") and your workflow runs at the local time you specify. Learn more in our documentation about schedules.

Join the discussion within GitHub Community.