Skip to content

pack: add --include-env - #55

Merged
manish-wekan merged 1 commit into
mainfrom
feat/pack-include-env
Oct 16, 2026
Merged

manish-wekan merged 1 commit into
mainfrom
feat/pack-include-env

Conversation

@manish-wekan

@manish-wekan manish-wekan commented Oct 16, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

  • Add nitrostack-py pack --include-env to include .env, .env.local, .env.production, and other .env.* secret files in the wheel (same set _is_secret_env already filters out).
  • Default behaviour is unchanged: secret env files stay excluded; .env.example is still always included.
  • When --include-env is used, the CLI prints a warning that lists the env file paths without printing their contents.

Behaviour

  • pack_project(..., include_env=False) threads the flag through collect_pack_files, staging, wheel build fallback, and post-build wheel injection.
  • --dry-run --include-env lists env files in the pack preview and shows the warning.

Tests

cd nitrostack-include-env && PYENV_VERSION=3.14.2 UV_PROJECT_ENVIRONMENT=/Users/mac/.claude/jobs/36afc995/tmp/sdkvenv-include-env uv run --extra dev python -m pytest tests -q

831 passed in ~8s (full suite).

Align Python pack with the TypeScript CLI: optional inclusion of .env
files in the wheel, with a warning that lists paths without printing values.
@manish-wekan
manish-wekan merged commit 93d6fcd into main Oct 16, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant