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.8.1521 and 1.9.1523 release notes and tags are currently unavailable #14092

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

Originally created by @BouwenMA on GitHub (Jun 3, 2021).

Originally assigned to: @DHowett on GitHub.

Already had v1.9.1445.0 updated several days ago, and just today had update come down from store for a version 1.9.1523.0. The "About" screen shows the newer 1.9.1523.0 version, the recent activity in the store for downloads and updates also shows the new 1.9.1523 version, yet the store page itself still reports it as v1.9.1445.0.

It is not readily apparent where this build came from given there are no matching tags/releases in the github repo.

Originally created by @BouwenMA on GitHub (Jun 3, 2021). Originally assigned to: @DHowett on GitHub. <!-- Briefly describe which document needs to be corrected and why. --> Already had v1.9.1445.0 updated several days ago, and just today had update come down from store for a version 1.9.1523.0. The "About" screen shows the newer 1.9.1523.0 version, the recent activity in the store for downloads and updates also shows the new 1.9.1523 version, yet the store page itself still reports it as v1.9.1445.0. It is not readily apparent where this build came from given there are no matching tags/releases in the github repo.
claunia added the Needs-Tag-FixIssue-Docs labels 2026-01-31 04:00:41 +00:00
claunia commented 2026-01-31 04:00:42 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (Jun 3, 2021):

Yeah sometimes the store release comes before the tags/releases in the Github repo.

where this build came from

Well, if you really want to know the answer, the build actually came from Microsoft internally. The Github repo does not contain all the needed things. There's a bunch of things needed inside Microsoft (for example, signing, localization, packaging, etc.) to publish a new release.

@skyline75489 commented on GitHub (Jun 3, 2021): Yeah sometimes the store release comes before the tags/releases in the Github repo. > where this build came from Well, if you really want to know the answer, the build actually came from Microsoft *internally*. The Github repo does not contain all the needed things. There's a bunch of things needed inside Microsoft (for example, signing, localization, packaging, etc.) to publish a new release.
claunia commented 2026-01-31 04:00:42 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 3, 2021):

Yes, sorry. I usually only tag the release after it's up on the store.

The delta you'll be interested in is v1.9.1444.0..release-1.9. Everything's there in the commit history for the 1.9 branch.

@DHowett commented on GitHub (Jun 3, 2021): Yes, sorry. I usually only tag the release after it's up on the store. The delta you'll be interested in is `v1.9.1444.0..release-1.9`. Everything's there in the commit history for the 1.9 branch.
claunia commented 2026-01-31 04:00:43 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 3, 2021):

Tags pushed; getting the release notes up.

https://github.com/microsoft/terminal/tree/v1.9.1523.0
https://github.com/microsoft/terminal/tree/v1.8.1521.0

@DHowett commented on GitHub (Jun 3, 2021): Tags pushed; getting the release notes up. https://github.com/microsoft/terminal/tree/v1.9.1523.0 https://github.com/microsoft/terminal/tree/v1.8.1521.0
claunia commented 2026-01-31 04:00:43 +00:00
Author
Owner
Copy Link

@BouwenMA commented on GitHub (Jun 4, 2021):

I suspected there may have been some other internal repo at Microsoft that was possibly ahead for commits or had unique items necessary for the store interaction. The confirmation and hearing the great explanation/background is very helpful. I appreciate the quick response from both of you. Thank you very much.

I did try to search first to determine the release flow/pipeline for projects like this, to see if it was documented prior to submitting this question, and do apologize if I missed that somewhere.

This can be closed as far as I am concerned (feel free to re-open if needed for other aspects). Even without the changelog itself yet there, being able to at least review the changes direct from the commits is helpful.

@BouwenMA commented on GitHub (Jun 4, 2021): I suspected there may have been some other internal repo at Microsoft that was possibly ahead for commits or had unique items necessary for the store interaction. The confirmation and hearing the great explanation/background is very helpful. I appreciate the quick response from both of you. Thank you very much. I did try to search first to determine the release flow/pipeline for projects like this, to see if it was documented prior to submitting this question, and do apologize if I missed that somewhere. This can be closed as far as I am concerned (feel free to re-open if needed for other aspects). Even without the changelog itself yet there, being able to at least review the changes direct from the commits is helpful.
claunia commented 2026-01-31 04:00:43 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 4, 2021):

Sorry about the miscommunication! The releases actually are built totally out of this repository :)

There are a couple overlay files but this is the only repository that we use.

@DHowett commented on GitHub (Jun 4, 2021): Sorry about the miscommunication! The releases actually are built totally out of this repository :) There are a couple overlay files but this is the only repository that we use.
claunia commented 2026-01-31 04:00:43 +00:00
Author
Owner
Copy Link

@vefatica commented on GitHub (Jun 7, 2021):

When will these be available on GitHub?

@vefatica commented on GitHub (Jun 7, 2021): When will these be available on GitHub?
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-Docs Needs-Tag-Fix
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#14092
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?