unwanted store dependency #23988

Closed
opened 2026-01-31 08:58:16 +00:00 by claunia · 3 comments
Owner

Originally created by @lbruno on GitHub (Jan 23, 2026).

Description of the new feature

follow-up from #19764 :

  • i was terribly surprised by how Terminal deps upon the store
  • i don't see what's the benefit that it brings
  • now, i did find a workaround/fall back

but honestly i'm kinda surprised by the store dep, and i'm opening this discussion to beg folks to consider removing this sharp corner

Proposed technical implementation details

No response

Originally created by @lbruno on GitHub (Jan 23, 2026). ### Description of the new feature follow-up from #19764 : - i was terribly surprised by how Terminal deps upon the store - i don't see what's the benefit that it brings - now, i did find a workaround/fall back but honestly i'm kinda surprised by the store dep, and i'm opening this discussion to beg folks to consider removing this sharp corner ### Proposed technical implementation details _No response_
claunia added the Issue-QuestionNeeds-TriageNeeds-Tag-FixResolution-Answered labels 2026-01-31 08:58:17 +00:00
Author
Owner

@lhecker commented on GitHub (Jan 23, 2026):

i was terribly surprised by how Terminal deps upon the store

Well, so were we. Our assumption was that our "appLicensing" capability in the manifest would prevent this. @DHowett has already engaged the relevant teams to ask if we did anything wrong, etc.

FWIW, you can always use our portable Terminal builds as a workaround in such situations.

@lhecker commented on GitHub (Jan 23, 2026): > i was terribly surprised by how Terminal deps upon the store Well, so were we. Our assumption was that our `"appLicensing"` capability in the manifest would prevent this. @DHowett has already engaged the relevant teams to ask if we did anything wrong, etc. FWIW, you can always use our portable Terminal builds as a workaround in such situations.
Author
Owner

@DHowett commented on GitHub (Jan 23, 2026):

Oh, yes, we are just as surprised as you are.

Behind the curtain a bit: we added a capability called appLicensing to our manifest to expressly prevent licensing checks. Before that, you couldn't even Add-AppxPackage on an airgapped machine. Why that doesn't apply here is the current mystery I'm talking to folks about.

@DHowett commented on GitHub (Jan 23, 2026): Oh, yes, we are just as surprised as you are. Behind the curtain a bit: we added a capability called `appLicensing` to our manifest to _expressly prevent_ licensing checks. Before that, you couldn't even `Add-AppxPackage` on an airgapped machine. Why that doesn't apply here is the current mystery I'm talking to folks about.
Author
Owner

@lbruno commented on GitHub (Jan 23, 2026):

much appreciate the extra context folks; will try switching to the portable build as yous suggest

@lbruno commented on GitHub (Jan 23, 2026): much appreciate the extra context folks; will try switching to the portable build as yous suggest
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#23988