General

Role of the registry

General is the default Julia package registry. The README explains that package registries are used by Julia's package manager Pkg.jl and include information about packages such as versions, dependencies, and compatibility constraints. In practice this means that when a Julia user runs a command to add a package, the resolver consults General to learn which versions exist, what each version requires, and which combinations are compatible. The registry is described as open for everyone to use and as providing access to a large ecosystem of packages, which is the point of a central index: it lets a global community share code through one trusted source. The README also points readers to community channels where new package registrations can be followed, specifically a #new-packages-feed channel in the Julia Slack and in Zulip. That gives interested users a live feed of what is being added without polling the repository. For package authors, the registry is the distribution mechanism, and for users it is the lookup table that makes versioned installation possible. The README frames General not as an application but as infrastructure, and most of its text is about how to interact with it correctly rather than what features it offers. Understanding this role is the first step to using Julia's packaging system well, because many installation and compatibility questions reduce to how the registry records a package's metadata.

Registering packages

The README explains that new packages and new versions of packages are added to General by pull requests against the GitHub repository. It strongly recommends using Registrator.jl to automate this process, and notes that Registrator can run either as a GitHub App or through a web interface. When Registrator is triggered it opens a pull request against the registry, and pull requests that meet certain guidelines are merged automatically, while others need manual review by a human. The README also recommends TagBot, which automatically tags a release in the package's own repository after the new release is merged into the registry. On licensing, the README states that registered packages must have an Open Source Initiative approved license, clearly marked via a license file in the package repository, and it gives detailed definitions of what counts as a README file, a license file, and a third party notice file. Packages that wrap proprietary or restrictive libraries are acceptable if those licenses permit open source distribution of the Julia wrapper code, with the more restrictive license mentioned in the third party notice or license file and preferably also in the README. These rules exist so that the registry stays coherent and legally usable, and they shift most of the mechanical work onto automated bots rather than manual editing.

Automatic merging and timing

The README details how pull requests into General are merged. Pull requests that meet certain criteria are merged automatically on a periodic basis, but only pull requests opened by Registrator.jl are candidates for automatic merging; everything else is reviewed by a person. The full set of guidelines lives in the RegistryCI documentation. The waiting periods are concrete: new Julia packages wait three days, which the README says allows time for community feedback, while new versions of existing packages wait fifteen minutes, and JLL packages, which carry binary dependencies, also wait fifteen minutes whether for a new package or a new version. These timings balance speed against the chance for someone to flag a problem, and the longer window for brand new packages reflects the higher risk of a mistaken or duplicate registration. The FAQ answers a common question directly: you do not need to register a package to install it. The README shows that a package can be installed straight from a Git URL using Pkg.add with the url argument or the Pkg REPL mode, and that the URL is then saved in the Manifest.toml so environments resolve consistently. This distinction is useful because it tells users that registration is about discoverability and versioning, not a hard requirement for running code. The repository is published under the MIT license and its most recent commit was on 2026-08-26.

Editorial conclusion

General is the default Julia package registry. The README explains that package registries are used by Julia's package manager Pkg.jl and include information about packages such as versions, dependencies, and compatibility constraints. The registry is open for everyone to use and provides access to a large ecosystem of packages. The repository is published under the MIT license and its most recent commit was on 2026-08-26.