Package registry for Kaimon Slate and its extension packages
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Kahli Burke 4f69083a10 Drop KaimonSlate and SlateExtensionsBase
Both are now in the General registry, so this registry no longer needs to carry them —
it serves the extension packages, which aren't in General.

Refresh the README and the package table accordingly.
2026-08-04 17:06:30 -07:00
B/BonitoSlate New package: BonitoSlate v0.1.0 2026-07-31 12:40:51 -07:00
C/CesiumSlate New package: CesiumSlate v0.1.0 2026-07-31 12:40:42 -07:00
G New package: GlobeSlate v0.1.0 2026-07-31 12:40:47 -07:00
S Drop KaimonSlate and SlateExtensionsBase 2026-08-04 17:06:30 -07:00
README.md Drop KaimonSlate and SlateExtensionsBase 2026-08-04 17:06:30 -07:00
Registry.toml Drop KaimonSlate and SlateExtensionsBase 2026-08-04 17:06:30 -07:00

SlateRegistry

A Julia package registry for Kaimon Slate extension packages that aren't in the General registry.

KaimonSlate and SlateExtensionsBase are in General — you do not need this registry to install Slate or to write an extension against the SDK. This registry carries only the extension packages themselves.

This repository is public and contains only package metadata — names, versions and repository URLs. Most of the packages it points at are private; installing those requires access to their repositories.

Use

Add the registry once per machine, from the Pkg REPL (press ]):

pkg> registry add https://github.com/kahliburke/SlateRegistry

It sits alongside General rather than replacing it — Pkg searches every installed registry, so ordinary packages keep resolving as usual. After that, an extension installs like any other package:

pkg> add SlateAssess          # into your notebook's environment

Registries are cached locally, so a newly published version isn't visible until you refresh:

pkg> registry update

If a package or version "does not exist" and you think it should, run that first — a stale registry is the usual cause.

Packages

Package Repository Visibility
BonitoSlate KaimonSlate.jl, examples/extensions/BonitoSlate public
SlateAFM KaimonSlate.jl, examples/extensions/SlateAFM public
StarRating KaimonSlate.jl, examples/extensions/StarRating public
CesiumSlate CesiumSlate.jl private
GiacSlate GiacSlate.jl private
GlobeSlate GlobeSlate.jl private
SlateAssess SlateAssess.jl private
SlateBench SlateBench.jl private
SlatePlotly SlatePlotly.jl private

Installing a private package needs git credentials for GitHub. The registry records repository locations as HTTPS URLs, so an SSH key alone is not sufficient — the simplest route is:

gh auth login          # choose HTTPS for the git protocol
gh auth setup-git      # writes the credential helper; a separate step, easily missed

Publishing (maintainers)

With LocalRegistry.jl, from the package's own checkout, after bumping version and pushing the commit:

using LocalRegistry
register("/path/to/Package.jl"; registry = "SlateRegistry", push = true)

Two things to remember: push the package commit before registering (the registry records a git tree SHA that has to be reachable), and register from a clean working tree — register refuses a dirty one, so use a fresh clone if your checkout has work in progress.