starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

1.1.2021.0 is Released, but not available in the MS Store #9727

New Issue
Closed
opened 2026-01-31 02:02:18 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 02:02:18 +00:00
Owner
Copy Link

Originally created by @IanKemp on GitHub (Jul 22, 2020).

I'm watching the Releases in this repo and got an email ~13 hours ago that v1.1.2021.0 has been released, which I assume means it's been pushed to the Microsoft Store. However, if I open the Store app on my PC, then go to "Downloads and updates" and click "Get updates", Windows Terminal is listed at version 1.0.1811.0 with no option to update.

Am I incorrect in assuming that a Release from this repo implies availability in the Store?

Originally created by @IanKemp on GitHub (Jul 22, 2020). I'm watching the Releases in this repo and got an email ~13 hours ago that v1.1.2021.0 has been released, which I assume means it's been pushed to the Microsoft Store. However, if I open the Store app on my PC, then go to "Downloads and updates" and click "Get updates", Windows Terminal is listed at version 1.0.1811.0 with no option to update. Am I incorrect in assuming that a Release from this repo implies availability in the Store?
claunia added the Issue-QuestionNeeds-TriageNeeds-Tag-FixProduct-Meta labels 2026-01-31 02:02:18 +00:00
claunia commented 2026-01-31 02:02:19 +00:00
Author
Owner
Copy Link

@Rob-Wal commented on GitHub (Jul 22, 2020):

I received the email as well and looking forward to this upgrade. The MSI is not available for download here on github either. There is also no release notes here yet. They either found a bug or the email went out early.

@Rob-Wal commented on GitHub (Jul 22, 2020): I received the email as well and looking forward to this upgrade. The MSI is not available for download here on github either. There is also no release notes here yet. They either found a bug or the email went out early.
claunia commented 2026-01-31 02:02:20 +00:00
Author
Owner
Copy Link

@kiehnek commented on GitHub (Jul 22, 2020):

v1.1.2021.0 and v1.2.2022.0 are no releases, but tags. These are just to mark specific timestamps in the code. maybe these tags will be the next releases, but they are not yet.

To get the preview versions of microsoft terminal, also make sure to download the Preview from the Microsoft store and not the regular Terminal.

Correct me, if I have said something wrong.

@kiehnek commented on GitHub (Jul 22, 2020): v1.1.2021.0 and v1.2.2022.0 are no releases, but tags. These are just to mark specific timestamps in the code. maybe these tags will be the next releases, but they are not yet. To get the preview versions of microsoft terminal, also make sure to download [the Preview](https://www.microsoft.com/store/productId/9N8G5RFZ9XK3) from the Microsoft store and not the regular Terminal. _Correct me, if I have said something wrong._
claunia commented 2026-01-31 02:02:20 +00:00
Author
Owner
Copy Link

@Rob-Wal commented on GitHub (Jul 22, 2020):

v1.1.2021.0 and v1.2.2022.0 are no releases, but tags. These are just to mark specific timestamps in the code. maybe these tags will be the next releases, but they are not yet.

To get the preview versions of microsoft terminal, also make sure to download the Preview from the Microsoft store and not the regular Terminal.

Correct me, if I have said something wrong.

I understand that, but I received an email with release notes for v1.1.2021.0 from Dustin. It rolls up the changes in the preview and more into the stable branch. So yes, that email was probably sent prematurely or they found a bug and delayed it.

@Rob-Wal commented on GitHub (Jul 22, 2020): > v1.1.2021.0 and v1.2.2022.0 are no releases, but tags. These are just to mark specific timestamps in the code. maybe these tags will be the next releases, but they are not yet. > > To get the preview versions of microsoft terminal, also make sure to download [the Preview](https://www.microsoft.com/store/productId/9N8G5RFZ9XK3) from the Microsoft store and not the regular Terminal. > > _Correct me, if I have said something wrong._ I understand that, but I received an email with release notes for v1.1.2021.0 from Dustin. It rolls up the changes in the preview and more into the stable branch. So yes, that email was probably sent prematurely or they found a bug and delayed it.
claunia commented 2026-01-31 02:02:20 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Jul 22, 2020):

@DHowett Can you republish the release if it was intended? This isn't the first time a release notification was sent but the Store wasn't updated. The github release page doesn't even have the msixbundle either for those who don't want to wait for the Store package to pickup (or can't use the Store).

@WSLUser commented on GitHub (Jul 22, 2020): @DHowett Can you republish the release if it was intended? This isn't the first time a release notification was sent but the Store wasn't updated. The github release page doesn't even have the msixbundle either for those who don't want to wait for the Store package to pickup (or can't use the Store).
claunia commented 2026-01-31 02:02:21 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 22, 2020):

I believe he's still drafting the official release notes. Your patience is appreciated, it is only 7am in Seattle after all ☺️

The Store does take some time to finish ingesting a release - sometimes up to 24 hours. So while it might not be available immediately on the Store, it is on it's way.

@zadjii-msft commented on GitHub (Jul 22, 2020): I believe he's still drafting the official release notes. Your patience is appreciated, it is only 7am in Seattle after all ☺️ The Store does take some time to finish ingesting a release - sometimes up to 24 hours. So while it might not be available immediately on the Store, it is _on it's way_.
claunia commented 2026-01-31 02:02:21 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 22, 2020):

The release was published to GitHub unintentionally and will be available at some future point.

@DHowett commented on GitHub (Jul 22, 2020): The release was published to GitHub unintentionally and will be available at some future point.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Question Needs-Tag-Fix Needs-Triage Product-Meta
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#9727
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?