hs project migrate does not migrate environment variables to v2026.03

[marcelsemasoft]

CLI Version

8.3.0

Node.js Version

25.8.1

Operating System

Windows 11

Description

Environment variables of serverless functions (2025.1) are not migrated when migrating to v2026.03

Secrets are correctly migrated, but thats not the case for environment variables.
It seems that 2026.03 does not support any env variables, but secrets should be the way to go.

Steps to Reproduce

1. Create project with 2025.1 and a serverless function (having an environment variable configured for the endpoint)
2. run hs project migrate
   IS: The entry is completely discarded, there is no warning and the migration completes successful

Expected Behavior

The environment variable is available or at least migrated to a secret.

Screenshots

No response

Additional Context

No response

[brandenrodgers]

Thanks for reporting this! The environment map in serverless.json was supported in platform version 2025.1 and earlier, but was removed in 2025.2 and 2026.03 in favor of the secrets system, which is more secure (values are encrypted and managed outside of your config file).

There's a workaround: Re-register your environment variable values as secrets using the CLI, then reference the keys in your *-hsmeta.json secretsKey array:

hs secrets add MY_VAR

Then in the *-hsmeta.json file:

{ "secretsKey": ["MY_VAR"] }

We have a fix in progress, but the workaround should unblock you in the meantime!