← Back to issue list

passthrough field being added to snap.yaml

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1862197
Type
issue
State
closed
Author
~ianmjones
Labels
—
Created
Updated
Closed

Current evaluation

App-level `passthrough` keys were copied verbatim into the generated meta/snap.yaml, triggering manual review on store builds. Fixed by merged PR snapcore/snapcraft#2914 (commit da9508fd3), released in snapcraft 3.10; passthrough is now dropped from snap.yaml.

Resolution: closed resolved

Reason: Maintainer ~cjp256 opened and merged snapcore/snapcraft#2914 ("meta: ensure Application passthrough is scrubbed for snap.yaml", commit da9508fd3) with unit and spread test coverage; ~sergiusens closed the bug as "Part of 3.10". Today snap_yaml.py no longer emits app.passthrough into snap.yaml, and docs instruct core20→core22 migration to remove passthrough keys.

Evaluated by: mr-cal-bot

No scores available.

Issue body

The last few automatic builds on snapcraft.io of my snippetpixie snap have been flagged for manual review each time because the resulting meta/snap.yaml has the `passthrough` field in its apps section. Apparently this in the snapcraft.yaml... ``` apps: snippetpixie: command: bin/desktop-launch $SNAP/usr/bin/com.github.bytepixie.snippetpixie passthrough: autostart: snippetpixie_snippetpixie.desktop desktop: usr/share/applications/com.github.bytepixie.snippetpixie.desktop environment: GSETTINGS_SCHEMA_DIR: $SNAP/usr/share/glib-2.0/schemas ``` ...results in the snap.yaml getting this... ``` apps: snippetpixie: autostart: snippetpixie_snippetpixie.desktop passthrough: autostart: snippetpixie_snippetpixie.desktop ``` This was discussed and the actual problem brought to my attention on the forum. https://forum.snapcraft.io/t/blocked-from-updating-snap-due-to-some-auto-revision-i-didnt-trigger/15309/10 The snapcraft.yaml that has surfaced this bug can be found in the snippetpixie GitHub repo. https://github.com/bytepixie/snippetpixie/blob/768d53503616a6cb5657bf296c3ce5ae2a06c348/snapcraft.yaml#L29

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved App-level `passthrough` keys were copied verbatim into the generated meta/snap.yaml, triggering manual review on store builds. Fixed by merged PR snapcore/snapcraft#2914 (commit da9508fd3), released in snapcraft 3.10; passthrough is now dropped from snap.yaml.
stealth/space-bunny-alpha — closed resolved Bug where an app-level `passthrough` key leaked into the built meta/snap.yaml, triggering store manual review. Fixed by merged PR snapcore/snapcraft#2914 (commit da9508fd3), shipped in snapcraft 3.10 per maintainer comments.
stealth/space-bunny-alpha — closed resolved Bug was fixed: snapcraft leaked the `passthrough` stanza into generated meta/snap.yaml, triggering manual review on store builds. Merged PR #2914 (commit da9508fd3, "meta: ensure Application passthrough is scrubbed for snap.yaml") and shipped in snapcraft 3.10.
stealth/space-bunny-alpha — closed resolved Fixed by merged canonical/snapcraft#2914 (commit da9508fd3), preventing app passthrough metadata from appearing in generated snap.yaml. Included in Snapcraft 3.10.
stealth/space-bunny-alpha — closed resolved Application passthrough was removed from generated snap.yaml by merged PR #2914 (commit da9508fd3), which also added unit-test coverage.
qwen/qwen3.6-35b-a3b — — Closed and likely abandoned. The reported duplication of the passthrough field in generated snap.yaml caused manual review flags on snapcraft.io. No resolution or fix was documented.
qwen/qwen3.6-35b-a3b — — Abandoned. Closed without resolution or comments. The duplicate passthrough field in generated snap.yaml remains unaddressed.
qwen/qwen3.6-35b-a3b — — Closed without resolution. The duplicate passthrough field in generated snap.yaml causing manual review flags was not addressed or fixed.
qwen/qwen3.6-35b-a3b — — Closed without resolution; likely abandoned. No fix documented for the duplicate passthrough field bug in snapcraft.yaml generation.
qwen3.6-35b-a3b-mtp-q6 — — Abandoned. The report described a bug where passthrough fields were incorrectly duplicated in snap.yaml, causing manual review flags on snapcraft.io.

Update history

Date Change
created

Related work

  • Likely Fixed By: snapcraft#2914 (confidence 97%)

    Merged PR cited by the reporter's fix comment; commit da9508fd3 scrubs Application passthrough from generated snap.yaml.

  • Superseded By: snapcraft#6124 (confidence 55%)

    Docs commit 5bbc654e3 (#6124) later documents removing passthrough for core22 migration, indicating passthrough is now a no-op/deprecated rather than forwarded.

  • Related To: snapcraft#2091 (confidence 45%)

    Earlier commit ed39df1a3 'meta: soften warning about using passthrough' (#2091) relates to the same experimental passthrough feature (#2053 added it).

Related issues

Issue Project State Summary Similarity
#2026 Implement a passthrough feature snapcraft closed Passthrough for new snapd keywords shipped in PR #2053 (commit f9b75a974, 'meta: implement passthrough of properties to snap.yaml'), later softened by #2091 and scrubbed for snap.yaml in #2914.
79%
#2053 meta: implement pass-through of properties to snap.yaml snapcraft merged Merged #2053 as f9b75a974, adding global and app-local passthrough metadata, ambiguity checks, and warnings for unvalidated snap.yaml properties.
74%
#2914 meta: ensure Application passthrough is scrubbed for snap.yaml snapcraft merged Merged PR #2914 fixed snap.yaml generation to scrub Application passthrough metadata; commit da9508fd3 added unit and spread coverage.
73%