Warn if `--platform` is used for remote builds
Metadata
Current evaluation
Enhancement: make snapcraft remote-build error when --platform is passed and recommend --build-for, since --platform was dropped in 8.7.0 with no in-tool notice. Triaged by maintainer; no implementation yet.
Suggested action: keep open
Reason: The issue is triaged (Status: Triaged, Type: Enhancement) and filed by maintainer mr-cal, with an internal ticket SNAPCRAFT-1013 created. The feature is not yet implemented: snapcraft/commands/remote.py only defines --build-for, so --platform on remote-build currently falls through to argparse's generic 'unrecognized arguments' error rather than the recommended helpful message pointing to --build-for. Related work: #5216 dropped --platform, and #5351 added early errors for invalid platform usage, but neither adds the specific --platform warning requested here.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
32.0
Staleness:
70
Complexity:
20
Confidence:
75
Support Request:
0
|
keep open | Enhancement: make snapcraft remote-build error when --platform is passed and recommend --build-for, since --platform was dropped in 8.7.0 with no in-tool notice. Triaged by maintainer; no implementation yet. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
90
Complexity:
15
Confidence:
85
Support Request:
0
|
keep open | Enhancement to warn or error when --platform is used with remote-build, directing users to --build-for instead. Currently triaged but inactive for over 15 months. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
10
Confidence:
60
Support Request:
0
|
close stale | Enhancement to add a warning when the deprecated --platform flag is used with remote builds. Triaged but inactive for 455 days with no progress or maintainer engagement. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
75
Complexity:
20
Confidence:
85
Support Request:
0
|
keep open | Add an error when --platform is used with remote builds, recommending --build-for instead. The flag was removed in v8.7.0 but lacked in-app warnings. Triaged enhancement with internal ticket created, awaiting implementation. |
Update history
No update history recorded yet.
Related work
-
Related To:
snapcraft/snapcraft#5216
(confidence 80%)
PR that dropped --platform from remote-build in 8.7.0, the change that motivated this enhancement.
-
Related To:
snapcraft/snapcraft#5351
(confidence 70%)
Added early errors for invalid platform usage in remote builds; related but does not add the --platform-specific warning.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #4881 remote build: fails if `--platform` or `--build-for` are passed with no `platforms` or `architectures` defined | snapcraft | closed | Closed pending implementation per defined scope: restrict --platform/--build-for flags to projects without explicit platform definitions and block their use for core22 snaps. Tracked in Jira CRAFT-3070. | |
| #5435 remote build: deprecate `--build-for` | snapcraft | open | Deprecate --build-for in snapcraft remote-build to align with Craft Application and other craft tools. Triaged by maintainer who confirmed it can ship in a minor release, but blocked by Launchpad's new build farm migration for --platform support. Code confirms --build-for is still active without deprecation warning. |