Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LibJS: Change URL and name to reflect move to LadybirdBrowser/ladybird #57

Merged
merged 1 commit into from
Jun 26, 2024

Conversation

ADKaster
Copy link
Contributor

Development of the cross-platform parts of LibWeb/LibJS/LibWasm for the Ladybird Browser project has split off into a new repository.

Point esvu to the new repository and its artifacts

@ADKaster
Copy link
Contributor Author

Windows CI failures unrelated (LibJS doesn't support windows anyway :D )

@devsnek
Copy link
Owner

devsnek commented Jun 26, 2024

@ADKaster i fixed the windows ci so you should be able to rebase main now

Development of the cross-platform parts of LibWeb/LibJS/LibWasm for
the Ladybird Browser project has split off into a new repository.

Point esvu to the new repository and its artifacts
@ADKaster ADKaster force-pushed the ladybird-browser-libjs branch from f3ed83b to e5b455a Compare June 26, 2024 00:39
@devsnek devsnek merged commit d7a4864 into devsnek:master Jun 26, 2024
8 checks passed
@ADKaster ADKaster deleted the ladybird-browser-libjs branch June 26, 2024 01:56
BertalanD added a commit to BertalanD/serenity that referenced this pull request Jul 7, 2024
As of devsnek/esvu#57, `esvu` now pulls the
LibJS binaries from the Ladybird repo, so these artifacts being created
has no purpose. As far as I can tell, nothing else uses them.

Maybe if the two LibJS versions start going their separate ways enough
to warrant both being available, we could consider re-adding this job.
But no point in using up CI resources for that right now.
ADKaster pushed a commit to SerenityOS/serenity that referenced this pull request Jul 7, 2024
As of devsnek/esvu#57, `esvu` now pulls the
LibJS binaries from the Ladybird repo, so these artifacts being created
has no purpose. As far as I can tell, nothing else uses them.

Maybe if the two LibJS versions start going their separate ways enough
to warrant both being available, we could consider re-adding this job.
But no point in using up CI resources for that right now.
alimpfard pushed a commit to alimpfard/serenity that referenced this pull request Jul 15, 2024
As of devsnek/esvu#57, `esvu` now pulls the
LibJS binaries from the Ladybird repo, so these artifacts being created
has no purpose. As far as I can tell, nothing else uses them.

Maybe if the two LibJS versions start going their separate ways enough
to warrant both being available, we could consider re-adding this job.
But no point in using up CI resources for that right now.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants