You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ChakraCore releases will be unavailable after 5/31/2024 #6991
The storage infrastructure for the ChakraCore releases is going away. As a result, the ChakraCore release downloads will not be available after 5/31/2024.
See details here: github.com/microsoft/ChakraCore-wiki/blob/master/Roadmap.md
There are still some projects using the legacy download structure.
We could download the binaries and attach them directly to the GitHub Releases.
(Including a deprecation warning)
There are still some projects using the legacy download structure.
We could download the binaries and attach them directly to the GitHub Releases.
(Including a deprecation warning)
This sounds like a good idea; I suppose we should also inform those projects.
@ppenzin maybe we could combine this action (re-hosting the last MS release and telling people who use it) with announcing a forthcoming non-MS release?
There are still some projects using the legacy download structure.
FWIW you can ignore the one in neoSphere - the engine hasn't been able to compile against 1.11 for a couple years due to needing top-level await support (ReportModuleCompletionCallback). I need to get rid of that makefile target and just direct people to build CC themselves.
@ppenzin@ShortDevelopment We are working on decommissioning the infrastructure that hosts these releases soon. Please let us know if you have been able to download any releases of interest or would like us to wait for a confirmation.
@ppenzin@ShortDevelopment We are working on decommissioning the infrastructure that hosts these releases soon. Please let us know if you have been able to download any releases of interest or would like us to wait for a confirmation.
Thank you for the warning I appreciate it - sorry I should have replied sooner; as @ShortDevelopment said I've taken a backup of the last releases.
@ppenzin@ShortDevelopment We are working on decommissioning the infrastructure that hosts these releases soon. Please let us know if you have been able to download any releases of interest or would like us to wait for a confirmation.
Thank you for the warning I appreciate it - sorry I should have replied sooner; as @ShortDevelopment said I've taken a backup of the last releases.
Activity
rhuanjl commentedon Apr 30, 2024
Thank you for this notification - I actually had assumed (without checking) that Microsoft would have taken down those releases some time ago.
@ppenzin FYI, if we want them for reference we should save copies of the last official CC releases within the next month.
ShortDevelopment commentedon Apr 30, 2024
There are still some projects using the legacy download structure.
We could download the binaries and attach them directly to the GitHub Releases.
(Including a deprecation warning)
rhuanjl commentedon Apr 30, 2024
This sounds like a good idea; I suppose we should also inform those projects.
@ppenzin maybe we could combine this action (re-hosting the last MS release and telling people who use it) with announcing a forthcoming non-MS release?
ppenzin commentedon May 1, 2024
I think we should do that, though not sure how many releases we need to download
ShortDevelopment commentedon May 2, 2024
Only the last 2 seem to be still available
fatcerberus commentedon May 2, 2024
FWIW you can ignore the one in neoSphere - the engine hasn't been able to compile against 1.11 for a couple years due to needing top-level await support (
ReportModuleCompletionCallback). I need to get rid of that makefile target and just direct people to build CC themselves.ShortDevelopment commentedon May 30, 2024
Maybe we could add some note like this to the current releases (See formatting):
Note
This release was provided by Microsoft
Caution
This release if out-of-support!
atulkatti commentedon May 31, 2024
@ppenzin @ShortDevelopment We are working on decommissioning the infrastructure that hosts these releases soon. Please let us know if you have been able to download any releases of interest or would like us to wait for a confirmation.
ShortDevelopment commentedon Jun 3, 2024
@atulkatti I'm not a core contributor but @rhuanjl has a backup of the latest release.
Btw: Thank you for the warning!! 🙂
rhuanjl commentedon Jun 3, 2024
Thank you for the warning I appreciate it - sorry I should have replied sooner; as @ShortDevelopment said I've taken a backup of the last releases.
atulkatti commentedon Jun 3, 2024
No worries. Thanks for the confirmation @rhuanjl and @ShortDevelopment. We will go ahead with the decommissioning of the infrastructure.
cooljeanius commentedon Jul 6, 2024
Are these backups available anywhere publicly?
ShortDevelopment commentedon Jul 8, 2024
@cooljeanius I made an unofficial backup myself.
Caution
This link is not controlled by the maintainers of this repo!
Please verify the signatures of the binaries and keep in mind that they are out of support!
update ChakraCore links
cooljeanius commentedon Jul 8, 2024
Thanks, this seems to work for my purposes. I've made backups to the WayBack Machine just in case!
Bump org.apache.maven.plugins:maven-release-plugin from 3.0.1 to 3.1.0 (