SNAPCRAFT_ environment variables not exposed to version-script
Metadata
Current evaluation
⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.
Abandoned and closed without resolution. The missing SNAPCRAFT_ environment variables in version-script were never addressed.
Suggested action: —
No scores available.
Issue body
```
Determining the version from the project repo (version-script).
+ init
+ local upstream_version packaging_revision
+ printenv
./snap/local/build-utilities/set-snap-version.bash: line 26: SNAPCRAFT_PROJECT_NAME: unbound variable
++ sed 's/^v//'
+ upstream_version=
The version-script failed to run (exit code 1)
```
in the set-snap-version.bash I was trying to get the upstream repo's version by calling:
```
git \
-C parts/"${SNAPCRAFT_PROJECT_NAME}"/src \
describe
```
This won't be possible if snapcraft doesn't expose the SNAPCRAFT_* environment variables like it usually does in other lifecycle steps.
NOTE the output of `printenv` in the trace, currently no environment variables are exposed at all.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Abandoned and closed without resolution. The missing SNAPCRAFT_ environment variables in version-script were never addressed. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The report details missing SNAPCRAFT_ environment variables in version-script execution, but zero comments and significant inactivity indicate the issue was abandoned without a fix. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Abandoned and closed without resolution. The version-script failed because SNAPCRAFT_* environment variables were not exposed during execution. No fix was implemented. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #4231 SNAPCRAFT_PROJECT_VERSION is empty if not explicitly set at top level | snapcraft | closed | Closed without a code fix. Maintainers explained dynamic environment variables are unsupported, and documentation was updated to clarify that SNAPCRAFT_PROJECT_VERSION only reflects statically set versions. | |
| #1822265 SNAPCRAFT_BUILD_ENVIRONMENT_* change doesn't apply to existing VMs | snapcraft (launchpad) | closed | Closed without resolution. SNAPCRAFT_BUILD_ENVIRONMENT_* changes failing to apply to existing VMs were left unaddressed with zero comments, indicating the report was abandoned or marked stale. | |
| #1533552 Please update snapcraft for new environment variables | snapcraft (launchpad) | closed | Closed without action or comments. The request to update snapcraft environment variable examples was abandoned, likely superseded by upstream snapd changes and subsequent tooling updates. | |
| #6025 Snapcraft ignores SNAPCRAFT_BUILD_ENVIRONMENT_* environment variables on MacOS | snapcraft | open | SNAPCRAFT_BUILD_ENVIRONMENT_CPU/MEMORY env vars documented for Multipass VM sizing are ignored on macOS; maintainer confirmed values are hardcoded, fix blocked by upstream craft-providers#531 (open 2+ years). Triaged as enhancement, no progress since Feb 2026. | |
| #2696 shell_utils: Add SNAPCRAFT_DEBUG_SCRIPTS env variable | snapcraft | closed | Superseded by another PR that implemented the SNAPCRAFT_DEBUG_SCRIPTS feature. Maintainers noted the merged code requires adjustments based on discussions in this closed request, which remains abandoned with unresolved review comments. | |
| #1876260 missing SNAPCRAFT_PART_* variables in override-prime | snapcraft (launchpad) | closed | Closed without resolution. The missing SNAPCRAFT_PART_* variables in override-prime remain unaddressed, likely abandoned due to inactivity. |