New tool: Julia

Abierto
  • ¿Algo no está bien?
#8,213 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@stemann ya está trabajando en esto.

Desde el 5/11/2026.

  • #8215 de @stemann — abierto

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
66/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
docker, julia, typescript
Área
build-system, tooling

Línea de trabajo

Start by reading the repository's existing tool definitions and tests for runtime-only tools; the issue does not name specific files, so locate those entry points first. Implement Julia installation and removal for the stated Linux architectures, then verify julia --version and the Pkg update command with a writable depot. Done means the tool can be installed and removed and both commands work.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Tool name

Julia

What is the tool used for?

Renovate's julia manager (renovatebot/renovate#42996) updates the [compat] entries of Julia Project.toml files. A follow-up would also update Manifest.toml, the lock file, which only Julia's package manager Pkg can write: Renovate would run Pkg in the repository. A manifest records the Julia version that wrote it (julia_version), and another Julia version rewrites it, so Renovate would install exactly that version.

Tool scope
  • Runtime only (CLI / binary)
Supported version range

>=1.6. Manifests record exact versions, such as 1.10.12.

Key commands that must work
julia --version
julia --startup-file=no --history-file=no --project=. -e 'import Pkg; Pkg.update(["Example"])'
Uninstall strategy

Remove the tool's install directory and its julia link. Pkg keeps packages and registries in JULIA_DEPOT_PATH, which Renovate points at its cache directory.

License of the tool (and any pre-built binaries)

MIT. The official binaries bundle third-party libraries under other licenses, including GPL-2.0+ parts of SuiteSparse: https://github.com/JuliaLang/julia/blob/master/THIRDPARTY.md

Minimal Dockerfile snippet
FROM ubuntu:24.04
ARG JULIA_VERSION=1.13.3
RUN apt-get update && apt-get install -y --no-install-recommends ca-certificates curl \
&& arch=$(uname -m) && dir=$([ "$arch" = x86_64 ] && echo x64 || echo aarch64) \
&& file="julia-${JULIA_VERSION}-linux-${arch}.tar.gz" \
&& curl -fsSLO "https://julialang-s3.julialang.org/bin/linux/${dir}/${JULIA_VERSION%.*}/${file}" \
&& curl -fsSL "https://julialang-s3.julialang.org/bin/checksums/julia-${JULIA_VERSION}.sha256" | grep " ${file}$" | sha256sum -c - \
&& mkdir -p /opt/julia && tar -xzf "${file}" -C /opt/julia --strip-components=1 && rm "${file}" \
&& ln -s /opt/julia/bin/julia /usr/local/bin/julia
Suggested tests
# Runtime
julia --version
# Pkg resolves a project against the General registry
printf '[deps]\nExample = "7876af07-990d-54b4-ab0e-23690620f79a"\n\n[compat]\nExample = "0.5"\n' > Project.toml
JULIA_DEPOT_PATH=/tmp/depot julia --startup-file=no --project=. -e 'import Pkg; Pkg.update(); Pkg.status()'
Any other relevant information
  • Julia publishes official tarballs for linux x86_64 and aarch64 for every stable release from 1.0.3, about 300 MB each, at https://julialang-s3.julialang.org/bin/linux/{x64,aarch64}/<major.minor>/julia-<version>-linux-{x86_64,aarch64}.tar.gz. SHA-256 checksums are in https://julialang-s3.julialang.org/bin/versions.json and https://julialang-s3.julialang.org/bin/checksums/julia-<version>.sha256. Versions are also GitHub releases of JuliaLang/julia.
  • Pkg needs a writable depot (JULIA_DEPOT_PATH) and network access to a package server (default https://pkg.julialang.org).
  • juliaup, Julia's version manager, can also pick the version from a manifest. Installing Julia itself lets Renovate pick the version, as it does for other tools.
Lenguaje dominante
TypeScript
Estrellas
58
Forks
65
Merge medio
6 h 47 min
PR fusionados (30 d)
504

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de containerbase/base

Todos los issues de containerbase/base

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.