VSCodium/vscodium
1
0
Fork 0
mirror of https://github.com/VSCodium/vscodium.git synced 2026-04-09 20:50:20 -05:00
Code Issues 135 Packages Projects Releases 10 Wiki Activity

Update loop from version 1.95.3 to 1.96.0 and back again #193

New Issue
Closed
opened 2025-09-10 23:42:41 -05:00 by giteasync · 2 comments
giteasync commented 2025-09-10 23:42:41 -05:00
Owner
Copy Link

Originally created by @docxml on GitHub.

When you upgrade from version 1.95.3 to 1.96.0 after restarting codium it reinstalls the previous version 1.95.3 and we enter an update loop.

Versión: 1.95.3 (user setup)
Release: 24321
Confirmar: dc5a551c256719475d2d0959270e3836c9bbb632
Fecha: 2024-11-16T09:16:49.983Z
Electron: 32.2.5
ElectronBuildId: undefined
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
SO: Windows_NT x64 10.0.19045

Versión: 1.96.0 (user setup)
Release: 24347
Confirmar: e4195c69747f84abd56a7d1d82fd9fa236511d26
Fecha: 2024-12-12T16:24:32.848Z
Electron: 32.2.7
ElectronBuildId: undefined
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
SO: Windows_NT x64 10.0.19045
Originally created by @docxml on GitHub. When you upgrade from version 1.95.3 to 1.96.0 after restarting codium it reinstalls the previous version 1.95.3 and we enter an update loop. ```plain Versión: 1.95.3 (user setup) Release: 24321 Confirmar: dc5a551c256719475d2d0959270e3836c9bbb632 Fecha: 2024-11-16T09:16:49.983Z Electron: 32.2.5 ElectronBuildId: undefined Chromium: 128.0.6613.186 Node.js: 20.18.0 V8: 12.8.374.38-electron.0 SO: Windows_NT x64 10.0.19045 ``` ```plain Versión: 1.96.0 (user setup) Release: 24347 Confirmar: e4195c69747f84abd56a7d1d82fd9fa236511d26 Fecha: 2024-12-12T16:24:32.848Z Electron: 32.2.7 ElectronBuildId: undefined Chromium: 128.0.6613.186 Node.js: 20.18.1 V8: 12.8.374.38-electron.0 SO: Windows_NT x64 10.0.19045 ```
giteasync added the bugstale labels 2025-09-10 23:42:41 -05:00
giteasync commented 2025-09-10 23:42:42 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub:

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment, and we'll keep it open. If you have any new additional information, please include it with your comment!

@github-actions[bot] commented on GitHub: This issue has been automatically marked as stale. **If this issue is still affecting you, please leave any comment**, and we'll keep it open. If you have any new additional information, please include it with your comment!
giteasync commented 2025-09-10 23:42:42 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub:

This issue has been closed due to inactivity, and will not be monitored. If this is a bug and you can reproduce this issue, please open a new issue.

@github-actions[bot] commented on GitHub: This issue has been closed due to inactivity, and will not be monitored. If this is a bug and you can reproduce this issue, please open a new issue.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
discussion
documentation
downstream
duplicate
enhancement
extension
good first issue
help wanted
invalid
never-stale
pull-request
Mirrored from GitHub Pull Request
 question
stale
telemetry
upstream
wontfix
No Label bug stale
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
giteasync
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: VSCodium/vscodium#193
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?