Release Notes

26.5.0

Features

Usability

• Redesigned job log viewer with faster loading, a searchable activity histogram, and smooth scrolling through large logs. (#21675)

• Jobs can now produce result files larger than 5 GB. (#22151)

• A project can now host multiple deployments, each with its own deployment specification. (#23103)

• Project deployments now control autoscaling per project: a deployment can be set to scale down to zero after a configurable idle period and to wake up automatically on the next incoming request. These settings are configured per project in the deployment settings, replacing the previous instance-wide keep-alive setting. (#22839)

• Deployment specifications can now request a sysimage build and carry environment variables, so a project's deployments can be tuned without changing the project's code. (#23875, #23874, #24416)

• The custom landing page is now a card within the configurable home screen layout, so administrators edit the welcome content and the rest of the home screen in one place. (#23313)

• Code, symbol and documentation search are now available as a versioned public API (/search/v1), with standard HTTP error codes, structured error responses and filtering by registry. This makes search usable from the jh command line and from agent tools. (#24098)

• The Pluto application now uses Pluto 1.0, the latest major release of the Pluto notebook environment. (#22806)

• Batch jobs that request a GPU now wait up to 72 hours for a GPU node to become available instead of failing after 30 minutes, and post an hourly status event while they wait. Interactive GPU jobs and CPU jobs keep the 30-minute limit. (#24250)

• Julia 1.13 images have been added and are now the default. (#24297, #24727)

• Folders in My Files and in Projects can now be downloaded as a single zip archive. (#14369)

Management

• Exporting a dataset to S3 now uses the dataset-import subsystem, making export behaviour consistent with import. (#22145)

• Enterprise and self-managed installations can now apply a per-registry cooldown to synced package registries, holding back newly published package versions for a configurable period. (#21876)

• Administrators can now delete a registry from its settings page, instead of the deletion requiring a manually run script. (#19665)

• Dataset imports now record who triggered a transfer and where the data came from, and surface those details to administrators as audit events. (#21897)

• Administrators can now configure the layout of the platform home screen, including which panels appear and how they are arranged. (#22802, #22803, #22804)

• Project deployments can now be given read and write access to a per-project folder in an S3 bucket. An administrator sets the bucket in the compute configuration, and each deployment receives credentials scoped to its own project folder plus the folder's address in its environment. Only enabled in enterprise installations. (#24028)

• Customer administrators can now browse and read other users' files from the user management page, through a new files.alluser API set. Each access is recorded as an audit event. (#23948)

• Administrators can now delegate home screen layout editing through a new layout.homepage API set, and every change to the home screen layout is recorded as an audit event. (#23984, #24165)

Fixes

Usability

• The job list now updates automatically when a job changes state, instead of requiring a manual refresh. (#15352)

• User environment variables are no longer limited to 1000 characters in total; the underlying storage column type was widened. (#21372)

• Fixed incorrect "DNS prefix already taken" errors when deploying an application or choosing a custom subdomain for a job or application. (#23019, #24949)

• Fixed a spurious error notification shown for project deployments that had in fact succeeded. (#23041)

• Improved the password entry widget used when opening a password-protected application, including a show/hide toggle and Return-key submit. (#23389)

• Fixed a database connection-pool defect that could abort long-running requests part-way through, causing intermittent server errors on slower operations such as creating a project or listing files. (#23481)

• Fixed a defect where enabling write access on a project dataset did not update the dataset list until the page was reloaded. (#23656)

• Fixed a defect where result links on the Symbol and Code search pages rendered without a target, so clicking a result did nothing. (#23638)

• Project job submission is faster and more reliable. The file service no longer re-downloads every package registry each time it bundles a project, and bundling now runs in its own short-lived process so it cannot stall other file operations. (#23695)

• Applications added from a Git repository now start the same way as project deployments, so code that finds files relative to its own folder works as expected. (#23824)

• A failed dataset upload now removes only the dataset it created. Previously the cleanup looked the dataset up by name when it ran, so if a newer dataset had taken that name by then, the newer dataset could be deleted instead. (#23953)

• Fixed an issue where opening a password-protected application could show an error page after the correct password had been entered, depending on the application URL. (#23412)

• Opening an application link now shows whether the application's job is starting, slow to start, failed or finished, instead of always showing "Connecting to your application". (#24580)

• Fixed an issue where a "Retry failed" request from the Sync Report was re-applied on every package sync, re-downloading the listed packages each time instead of once. (#24596)

• Fixed an issue on enterprise installations where logging out and immediately logging back in could show an error page. (#24503)

• Project Owners and Editors can now download the result files of batch jobs that other users ran from their Project. Previously they could see these files and save them to the Project, but downloading one failed with a permission error. (#24915)

• The Download CSV button on a registry's Sync Report is now available as soon as the report loads. Previously it stayed disabled until a column filter was applied. (#25077)

• Fixed the Details button in the Applications list opening a broken job page for an application with one running instance and no web interface. (#24904)

• Fixed two issues with short batch jobs: a job that finished successfully could be shown as Stopped, and its log output could be missing from the log viewer. (#24839)

Management

• The package Registrator now re-authenticates the user after an EOF error instead of failing the registration. (#22912)

• Fixed a defect where editing a credential in admin settings without re-entering its secret stored an empty token. (#23343)

• Fixed an issue where cached package registry access data could grow without limit and gradually fill the platform's storage. (#24265)

• SSH credentials for private registries configured by administrators now apply per host and take effect without a restart. This fixes connection failures on installations with many SSH credentials. (#24007)

• Improved the stability of Kubernetes installations: platform services now reserve the memory they need, so they are no longer evicted when a node runs short of memory. (#23551)

• Customer Administrators can now rerun, reproduce and add to a time capsule jobs started by other users. Previously Rerun and Reproduce were offered but refused, and adding another user's job to a time capsule reported success without saving it. (#24527)

• Customer Administrators can now retry failed packages from a registry's Sync Report. Previously the Retry Failed button was refused for them. (#25122)

Security

• This release includes security hardening in user onboarding and entitlement handling. Customers are encouraged to stay current with the latest release. (#22621)

• Customer Administrators can no longer change the API access controls of the Customer Administrator role. Only Platform Administrators can. (#24531)

26.4.5

Fixes

Usability

• Fixed an issue on Kubernetes installations where, after an upgrade, some pages could show missing data (for example, an empty application list when creating a Project) until platform services were restarted. (#24838)

• Fixed job logs on Kubernetes (Helm) installations not being archived, so the logs of older jobs stopped being available once the log retention period passed. (#24868)

• Re-running the Julia install script from a JuliaHub server now upgrades an existing juliaup installation. (#24856)

• Fixed a "Secrets manager not configured" error that requests using secrets could return for a short time after the platform restarted. (#25088)

• Fixed the Packages page loading slowly, or timing out, for a short time after the platform restarted. (#25089)

26.4.4

Fixes

Usability

• Fixed an issue where starting a job from a Project required a Manifest.toml, even for jobs that do not use Julia packages, such as R or shell jobs. (#24508)

• Fixed juliaup self update failing against a JuliaHub server when the server advertised a juliaup version it did not host. (#24827)

• Package documentation built with recent Documenter versions now shows the "not the latest stable release" banner on older versions, and the banner links to the newest release. (#24773)

• Fixed package sync dropping package versions whose artifacts are downloaded through a cache server, when the cache server's credentials did not match the artifact's original location. (#24786)

Management

• Fixed an issue where project owners could not assign their projects to collections. Previously only administrators could. (#24787)

Security

• This release includes security hardening in interactive application access. Customers are encouraged to stay current with the latest release. (#24625)

26.4.3

Fixes

Usability

• The access-option selector for applications and project deployments now states who will be able to reach the application under each option, with additional guidance when an application is made public. (#23993)

• Self-managed installations no longer show a "Billing is not configured" warning when launching jobs and applications. (#24489)

• Fixed an issue where package synchronization could stall for hours, delaying package version and documentation updates. (#24562)

• Fixed an issue where users with a running job could be refused a new job or application launch with "User monthly limit exceeded" while well below their monthly limit. (#24546)

• Fixed an issue where the "Click here to enter the notebook editor" button on a notebook page did nothing, so the notebook could not be opened for editing. (#24535, #24537)

• Fixed an issue where package registrations stayed pending and showed "Registration is stalled" on installations without an OAuth authorization provider, such as those whose registries authenticate with an access token. (#24491)

Management

• Fixed an issue where the package policy editor could save a different "block unspecified packages" setting than the one it showed. (#24477)

Security

• This release includes security hardening in notebook editing, interactive application sessions, and application request routing. Customers are encouraged to stay current with the latest release. (#24586, #23201, #23202, #23992, #24588)

26.4.2

Features

Management

• Windows Workstation is now supported on self-managed Kubernetes AWS installations. (#24316)

Fixes

Usability

• Fixed an issue where a brief loss of database connectivity during package synchronization could silently stop package version and documentation updates until the service was restarted. (#24074)

• Fixed a sign-in loop when authenticating from VS Code or the Julia REPL on installations whose identity provider does not issue refresh tokens. Sign-in previously succeeded and then immediately prompted for a new sign-in. (#24132, #24160)

• Fixed an issue on Kubernetes installations where projects were bundled against the public package server instead of the installation's own registries, so packages from private registries could not be resolved when running jobs or applications from a project. (#24242)

• Fixed an issue where a project could become stuck while its workspace was being reset if files were being listed at the same time, leaving the project unusable until the service was restarted. (#24408)

• Fixed the Stop Job button on the job details page, whose label was unreadable on hover. (#24394)

Management

• Fixed an issue where the registry settings page showed an empty form and errors for package registries accessed through a GitHub App. Registry syncing was unaffected. (#23844)

• Fixed an issue where the platform's session and cache store could grow until its storage volume filled. The store is now compacted on every start. Kubernetes installations can also configure the size of this volume. (#24366, #24267)

26.4.1

Fixes

Usability

• Fixed an issue where cloning a project along with all of its content could leave the copy's Source tab unusable - file listing, file view and downloads all failed - when the original project was created before the default branch name changed to main. (#23854)

• Fixed a slowdown where creating or opening a project could stall for users with a large number of projects, causing job and application submissions to time out. (#23689)

• Fixed an issue where package synchronization could stop after a temporary connectivity problem and not resume, leaving package listings out of date. (#23971)

Management

• Fixed a failure saving a package registry configuration when the registry is reached over SSH. Saving such a registry previously failed validation with a generic fetch error. (#23985)

Security

• Security hardening in project deployment packaging. Projects are now packaged from a point-in-time snapshot with stricter validation of project contents and dependencies, and deployment requests are validated more strictly. Customers are encouraged to stay current with the latest release. (#24027)

26.4.0

Features

Usability

• Projects now show a commit history listing with an upstream branch selector, making it easier to review and navigate changes in a Project. (#22113, #19725, #19726, #22757)

• Project publish requests can be reviewed and individually approved or denied. The collaboration UI now shows how many pull requests are open and lets reviewers jump between diffs with prev/next buttons. (#16204, #21203, #19521, #19081, #22073)

• Project templates updated: added a basic HTTP.jl web application template and removed the legacy Dash and Genie templates. (#22393, #22394)

• The job summary details view now shows whether the configured number of processes is per node or per vCPU, making a distributed job's process configuration and its cost implications clearer. (#22515)

• The project creation wizard's deployment step now offers a direct machine-type selection instead of preset plan options, giving a clearer, more consistent choice of compute when deploying an application from a project. (#22332)

• Deploying applications from a project is now a first-class flow: a new top-level Deployments list (separate from the Jobs list), a Deployment tab on the project details page showing current deployment status, and a "deployable" checkbox on the first page of the project create wizard. (#22330, #22392, #22747)

• Projects now support different Git branches between the upstream and the user's workspace, letting each user create and work on multiple branches (similar to GitHub); Start job, launch, and Deploy actions are disabled for branched projects. (#18645, #22838)

Management

• A new API Access Control admin view lets customer admins customize platform API access levels for non-administrator principals, overriding the shipped defaults per site. Site customizations are tracked with full change history and generate audit events; access control for administrator principals is protected from modification. (#21277)

• Enterprise and self-managed installations can now opt in, via a Helm chart flag, to hosting the DyadRegistry locally and proxying the Dyad juliabin channels through their own instance, so Dyad package operations authenticate against the local instance instead of the public JuliaHub. (#21877)

Security

• New Global CVE listing surfaces all security advisories reported against package registries, sorted by date, with a dedicated detail page for each advisory. (#21540, #22250)

Fixes

Usability

• Projects now enforce mutual exclusivity between deployable (web application) and batch job modes — a deployable project no longer exposes batch job actions, and a batch job project no longer accepts deployment submissions. (#22144)

• Log viewer performance is substantially improved, with faster loading and rendering of job logs. (#22185)

• The job Submit UI now correctly picks up the user's preferred application timeout and node size when starting a new job. (#21893)

• SharePoint dataset import: when the supplied URL points to anything beyond the site root (for example a document library path), users now see a clear error instead of a silent failure. (#22240)

• Julia precompilation in jobs now respects the job's CPU allocation (via JULIA_NUM_PRECOMPILE_TASKS), preventing out-of-memory failures during precompilation. (#22232)

• Symlinks inside a Project directory no longer cause batch job submissions to fail during bundling. (#20929)

• Fixed a project deployment that, after being suspended and resumed, failed to refresh its job token in the controller-sidecar, resulting in 403 errors downloading input files. (#22330, #22392, #22747, #22493, #22807)

• Fixed the symbol indexer so it indexes Base and the bundled standard libraries; searching for a standard-library symbol definition (for example base64encode) now returns results instead of nothing. (#22883)

• Fixed a failure that prevented R batch jobs from launching when started from a project's batch job specification. (#22680)

• Stopping a running job now uses a consistent in-app confirmation dialog across the Home page, job list, and job details pages, replacing the previous browser confirmation prompt. (#22157, #22160, #22161)

Management

• Credential and registry changes now take effect immediately: adding a new Personal Access Token or GitHub App, and enabling registration on a registry, no longer require a restart of the backend service before the change is usable. (#22212, #23083)

• SSO groups with no remaining user assignments are now cleaned up automatically on user login, preventing stale groups from lingering in registry settings and group lists. (#17767)

• The package activity table is now partitioned, keeping recent activity data hot while moving older entries out, improving query performance and reliability of package analytics. (#20962)

• Fixed a crash in the billing service that occurred when billing was disabled (no active pricing plan configured). (#22427)

• Adding a package registry now surfaces clearer, more descriptive errors when the configured GitHub App or Personal Access Token does not have access to the registry, instead of a generic "download failed". Also improves handling of intermittent failures in the add-registry flow. (#22109, #22162)

• Fixed an access issue when listing or updating datasets in a project where the user has customer admin-level access but is not directly a member. (#22525)

• Removed an administrator menu entry for Dyad plans that was not functional on Enterprise and self-managed deployments. (#22607)

• Improved how packaged Julia binaries are retrieved for downstream deployments, making juliaup distribution more reliable. (#21300)

• Fixed an issue where the package registry synchronize action could appear available again briefly after being triggered; the control now consistently reflects that a sync is in progress. (#14830)

• A new package search indexer is now enabled by default; new installs receive it from seed config and existing installs are switched to it during the upgrade. This new indexer is much faster and more memory efficient. (#22682)

• Fixed two ordering bugs in fresh chart-based platform bring-up that left the admin settings catalog (products, image groups, product families, features) incompletely applied on first run, which could cause jobs to fail to launch. (#23092)

Security

• Audit event generated for when a user aborts a dataset upload; the event now reflects the aborted outcome. (#20307)

• Fixed a privilege-revocation bug where a user temporarily granted the customer-admin role retained access to the IQOQ app after the role was revoked; feature permissions granted by a role are now reverted when the role is removed. (#22294)

• This release includes security hardening in the notebook viewer, application launch handling, and project permission enforcement. (#23155, #22606, #23300)

26.3.8

Fixes

Management

• Fixes for credentials admin page loading speed when using Github Enterprise. (#22455)

26.3.7

Fixes

Usability

• Fixed an issue where installing a Julia version via juliaup could fail because the required version metadata was missing. (#22821)

• Fixed an issue where package documentation could stop updating after a documentation link became broken. (#22819)

• Fixed the Julia installation script served by the platform so it directs clients to the correct package server. (#22818)

• Fixed an error that could prevent jobs from being submitted when a job image did not declare its API version. (#22611)

Management

• Fixed a redirect loop that could cause sign-in to fail with a 502 error when the platform runs behind a proxy that terminates HTTPS. (#22822)

• Removed spurious readiness warnings on deployments that run without compute enabled. (#22778)

Security

• Fixed an issue on platform.juliahub.com that could cause users to be repeatedly signed out with a "Session Expired" error until the platform was restarted. (#22709)

26.3.6

Fixes

Usability

• Fix for app browser sessions timing out and running into unauthorized loops. (#22706)

Security

• Security fixes. (#22712, #22711)

26.3.5

Fixes

Usability

• Fix for datasets and Git LFS in platform installs located in AWS regions other than us-east-1. (#22676)

• Fix for IQOQ app running against platforms that use a custom certificate authority. (#22688)

26.3.4

Fixes

Security

• Security fixes (#22665)

26.3.3

Fixes

Usability

• Fixed an issue where adding a new credit card did not replace the previous card as the default. (#22578)

• Fixed a crash in package registry sync when running for the first time. (#22564)

Security

• Fixed a bug where API authentication could incorrectly clear a user's SSO group memberships, removing their access to datasets and projects granted via those groups. (#22599)

• Security fixes (#22636)

26.3.2

Fixes

Usability

• Fixed an issue where anonymous visitors to /ui/Packages on juliahub.com were redirected to the homepage instead of seeing the public package listing. (#22547)

26.3.1

Fixes

Management

• Customer admin can now scan projects from another user (#22228)

• Fixed a startup failure in approuter/web/auth services on self-managed installs that use Embedded PostgreSQL (#22317)

Security

• Fixed a vulnerability where a user could submit jobs against a project they did not have access to, which could expose that project's secrets. (#22488)

26.3.0

Features

Usability

• Project file uploads now support files up to 5 GB (previously 2 GB), matching the git LFS maximum. (#21111)

• Administrators can now disable the Overwrite button in the Project merge conflict window, restricting users to the Merge option only. (#21112)

• Usage Reports have been moved from the Profile menu to the Admin menu, centralizing Business Admin and Platform Admin features. (#20945)

• The IQOQ application is now available to Customer Administrators, providing a way for them to run their own qualification activities. (#21809)

Management

• Customer Administrators can now set up and maintain private package registries without requiring Platform Admin access. (#18963)

• Administrators can now set a default limit on the number of nodes for Batch Jobs. (#21787)

Security

• Added Trivy-based vulnerability scanning (CVE detection) for Julia codebases and packages, including those on private registries. (#18702)

Fixes

Usability

• The authenticated package server is now enabled by default for platforms using external TLS termination. (#19933)

• Fixed a bug where the "Upload new version" button incorrectly appeared in the Project files modal; it now only appears for Datasets. (#21660)

• Fixed a bug where the project name warning sign appeared on the wrong tab (Template) instead of the Project Details tab. (#15267, #21791)

• Project jobs are now visible to all project editors and viewers, not just the user who launched the job. (#20682)

• Windows Workstation no longer displays noisy loading messages when starting up. (#20264)

Audit

• Audit events are generated when users are made or removed from the Customer Admin role. (#21775)

• Job audit events now include product and job type. (#21625)

• Audit events for Project Collections now use human readable names instead of "dag_*". (#21770)

• Project audit events now include the project name. (#21905)

• Audit events are now generated for application version management activities (new, add, modify, delete). (#21767)

26.2.0

Features

Usability

• Job log downloads now include all logs (not just those loaded in the browser) and are available in plain text format. (#20767, #19023)

• Windows Workstations now support full hibernation, allowing users to pause and resume sessions while preserving state. (#21141)

• Users can now view their Dyad AI daily and monthly spend limits and usage directly in the JuliaHub platform. (#21143)

• JuliaHub Platform now supports self-managed deployment on Microsoft Azure in addition to AWS. (#10321)

Management

• The Admin Summary view has been removed, as compute usage information is now available through monthly compute usage reports. (#20944)

Fixes

Usability

• Job stop and suspend confirmation dialogs now use in-page modals instead of browser pop-ups, ensuring users can always stop or suspend their jobs even when browser pop-ups are disabled. (#21236)

Management

• Customer Admin users can now correctly disable platform features for users and groups; previously the toggle would revert to enabled. (#20943)

• The feature management admin screen now correctly shows features as enabled for all users, with a visual indicator that the feature is enabled. (#21185)

26.1.5

Fixes

Usability

• Fix for allowing some users to continue to use their Dyad plan until the cancellation date (#22092)

Management

• Fix for allowing some users to revert their Dyad plan cancellation (#21978)

Security

• Security fixes (#22438, #22439)

26.1.4

Fixes

Management

• Assorted Helm Chart fixes (#21839, #21825)

26.1.3

Features

New

• Dyad Agent Subscriptions are here! (#21717)

Management

• Helm chart now supports customizable Kubernetes labels and annotations (#21715)

Fixes

Usability

• Fixed an error when adding certain Julia packages due to upstream Github reliabiltiy (#21636)

• For individuals on juliahub.com, fixed invoice PDF downloads triggering a browser security warning (#21582)

26.1.2

Fixes

Security

• Security fixes (#21449)

26.1.1

Fixes

Security

• Security fixes (#21436)

26.1.0

Features

Usability

• Distributed jobs now include pod id in log metadata, enabling log filtering for individual workers without JuliaHubLogging. (#20707)

• Windows Workstations now support hibernation, allowing users to pause and resume sessions while preserving state. (#19877)

Management

• Long-term token expiration dates are now visible in the UI for Instance Administrators. (#20500)

• GitHub Personal Access Token credentials now display metadata including expiration date. (#20170, #20698)

• Customer Admins can now manage application versions through a new admin UI, selecting which versions are available to users. For team installations, app versions update automatically to the latest release. (#20320, #20831)

• IQOQ validation reports can now be generated directly within JuliaHub by running the IQOQ app, enabling admins and self-managed customers to produce compliance documentation on-demand. (#20567)

Security

• Project jobs tracker now filters out other users' IDE/deployment jobs and restricts job actions (Re-run, Extend, Stop) to job owners only. (#20385)

Fixes

Management

• Customer Admin role now has Owner privileges in all projects. (#20924)

Audit

• Customer Admin role can now download audit event exports (#20651)

25.10.5

Fixes

Usability

• Fix for faster session checking in applications proxy (#22077)

Management

• Fix for SSO groups being removed during application launch (#22601)

25.10.4

Fixes

New

• Fixes for Dyad julia installer (#21158, #21155, #21166, #21179, #21156, #21242)

Management

• Fix Customer Admin access for creating snapshots of Windows Workstation instances to build custom AMIs with organization-specific tools and configurations pre-installed (#20343)

25.10.3

Fixes

New

• Fixes for Dyad julia installer (#21152)

25.10.2

Fixes

Usability

• Improved sync status message when there is a delay before sync retry (#20994)

• Added download support for juliaup channels on Windows (MSVC) and FreeBSD platforms (#21079)

• Fixed Julia package artifact downloads from non-GitHub sources (#20998)

25.10.1

Fixes

Usability

• juliaup release channels now synchronize correctly. (#20713)

25.10.0

Features

Usability

• Deprecated "Audit Logs" user interface has been completely replaced by "Audit Events" user interface. (#19007)

• juliaup release channels are now synced as part of the package sync process (#20713)

New

• Dataset Import now supports Sharepoint and OneDrive and has specific authentication flow. (#16472)

• Batch jobs can now be run on projects. Project batch job outputs can now be downloaded with configurable output directory. (#16724)

• Customer Admin users can now create system snapshots for Windows Workstation. (#18080)

Management

• Github Enterprise Server is now supported for Julia registries and packages for self-managed installations. (#16890)

• Package policies feature moved out of beta status. (#18973)

Security

• Julia Package registration now requires HTTPS for GitHub, GitLab, and Bitbucket. (#20192)

Fixes

Usability

• Version-less datasets are now visible in the UI. (#10658)

• Dataset uploads that fail will still show in UI, allowing the user to re-attempt upload. (#13511)

• Dataset uploads can now be aborted by users. (#19755)

• Fixed error when registering packages due to Github rate limits. (#20295)

Audit

• Private registry configuration changes now generate Audit Events. (#17368)

• Fixed filtering issues in Audit Events interface. (#17871)

• Customer administrators can now download audit event data. (#20651)

25.8.5

Fixes

Management

• When running behind a reverse proxy, JuliaHub now respects the X-Forwarded-Proto header for HTTP redirects. (#20574)

• The self-managed Helm chart now supports configurable environmental variables. (#20589)

• Fix for Github Enterprise installs using a Github application (#20672)

25.8.4

Fixes

Management

• Fix issue with cloning non-Github Julia package Git sources when using username and password. (#20348)

• Fix issue with date selection on package access admin report (#20292)

25.8.3

Fixes

Usability

• Suspending a project deployment now shows job as completed, not failed. (#20145)

• Fix for private registry cloning over SSH (#20284)

25.8.2

Features

Management

• Compute usage report is available to Customer admins. (#20157)

Fixes

Management

• Audit event streaming now includes package, registry and artifact download events. (#20010)

• searchsrvr memory limit increased to compensate for private registries. (#20239)

• Fix upgrade migration to update older configuration to avoid path not found errors. (#20241)

25.8.1

Features

Usability

• Large files within Projects are now transitioned into Git Large File Storage (LFS) when published or transferred. When Projects workspaces are reset, Git LFS files are pulled. (#16132)

• Dyad packages can now be filtered for in the packages list (#17849)

Management

• Registry sync interval for specific registries can now be adjusted by admins (#19438)

• Julia setup bootstrap now uses juliaup and sets up authentication (#17353)

• Github Apps can be used for authentication to private Julia registry Github repositories and Github Enterprise can be configured. (#16756)

• Datasets can be bulk uploaded via the browser and drop & drop (#17793)

• Global package policy can be applied to all packages across an install. (#19299)

• Registry sync can be forced and be registry specific. (#19439)

• Registry force sync button has been moved to Registries page. (#19440)

25.7.2

Fixes

Usability

• Fixes issues when downloading large audit event CSV files (#19650)

• Fixes HTTP proxy connectivity issue introduced in 25.7.1 (#19650)

25.7.1

Fixes

Usability

• Fixes sporadic dataset upload issue introduced in 25.7.0 (#19671)

• Fixes audit event download issues introduced in 25.7.0. (#19707)

• Fixes custom landing page content disappearing issue introduced in 25.7.0 (#19708)

• Lower DNS cache TTLs within internal load balancer to fix bad lookups (#19692)

25.7.0

Starting with 25.7.0, the JuliaHub Platform will be moving to monthly releases where the version will match YY.M.x where YY is the last two digits of the year, M is the month number, and x is an incrementing number (i.e. patch versions).

Features

Usability

• Applications can be configured for custom ordering on applications page. (#18463)

• Improved file viewer for project files within the web interface (#18477)

• "Datasets" tab within a project has been renamed to "Linked Data" (#19067)

• Multiple Julia versions can now be used for batch jobs. (#18574, #13681)

New

• Time Capsule to group reproducable jobs together is now generally available. (#13767)

Fixes

Usability

• Clone project has been moved to under "Manage" project menu. (#18723)

• "Collaborative editing" for projects has been renamed to "Group editing" (#16485)

• Much improved local Julia pkg authentication to JuliaHub resulting in less required refreshes and errors (#17610)

• Audit event export CSV files are now generated server-side greatly increasing its robustness (#17955, #18296)

• Non-admins can force a package sync (#19206)

• Julia standard library docs now use the current registered Julia version and show newer docs (#19296)

6.9.3

Fixes

Usability

• Fixed many small issues with the job logs viewer (#17898)

• Fixed issue with UI showing as synchronizing when already finished (#19090)

• Fixed issue with static analysis report display when all registries are enabled for static analysis (#18828)

6.9.2

Fixes

Usability

• Fix missing embedded images in generated Julia package documentation (#19043)

• Fix missing log gap in older job logs (#19019)

Security

• Security update for path escaping in various Julia dependencies used in Julia package registration (#19089, #19015)

• Security update for HTML sanitization in generated Julia documentation reported in GHSA-3mj7-qxh9-6q4p and CVE-2025-52561 (#19108)

6.9.1

Fixes

Usability

• Timestamps in Last Sync details now show correct time for Last Initiated and Last Successful (#18727)

• Restored back to one click application launch on Home page (#18812)

• Corrected Job details metrics display loading (#18768)

• Faster response times for requests using tokens (#18904)

• Corrected Project static analysis UI loading (#18551, #18828)

• New user registered applications correctly show up on applications page (#18814)

• Packages usage report uses correct date range including first and last day (#18940)

• Images generated during Julia package documentation generation show correctly (#17802)

• Dataset upload from Julia IDE shows notification on success or failure (#18631)

Audit

• Improved audit event latency for Julia package access when using NFS storage (#18835)

• Audit events generated for Julia package registry privilege changes (#18918)

6.9.0

Features

Usability

• New Getting Started Page (#17429)

• Usernames instead of Names are shown in project permissions and show user details in popover. (#17378, #18318)

• Project file listing reflects on-disk updates automatically and can be manually refreshed (#16153, #17329)

• Multi-resource projects will get migrated to single resource projects (#17216)

• Account deletion request form is now visible within Prefrences (#17704)

• Password authentication is available for all types of applications and project deployments. (#13565, #16660)

• Username is now visible within Preferences (#7683)

• Private Julia package registries can now be shared with user groups. (#16050)

• Usernames instead of Names are shown in project permissions and show user details in popover. (#17378, #18318)

New

• Projects can be organized into collections. (#17775, #17925)

• Subdomains for jobs and project deployments can be reserved before launching (#16500)

• Project editors can now upload dataset versions of other users that are shared within the project. (#17301)

• Kubernetes packaging is now available as Helm chart (#17289)

• Project deployment secrets are accessible to non-Julia based deployments (#16660)

• Projects can be scanned for static analysis to find Julia code issues (#17928, #17317)

Management

• Sync Report for package sync status visible to admins (#17030, #17029)

• Customer admins can view storage usage consumed by users (#18037)

Audit

• Registry and package audit events now include UUID and Julia version (#16440)

Fixes

Usability

• Search for attaching datasets to projects is clearer (#15077)

• Staged users now show up immediately in the users list

• Notebook folder now doesn't allow folder uploads with extensions like ".jl" and ".ipynb" (#17504)

• Project renaming now only shows success message (#17547, #17771)

• Dataset names now allow "." and can start with numbers (#16817)

• Progress bar is show when uploading datasets. (#16513)

• "Files" on sidebar is now called "My Files" to be clearer (#18187)

• Fix for air-gap fresh installations failing to start documentation generation (#18247)

• Date/time is formatted consistently across the platform (#17808)

• Dataset usernames now match usernames exactly (#8061)

Management

• Display timeout errors appropriately when downloading audit events. (#18285)

Security

• Private registry documentation access is checked against user's registry access authorization (#16657)

6.8.5

Fixes

Usability

• Fixes intermittent issue with hanging package sync. (#17975)

• Reenable new Project Genie Deployment template. (#17991)

• Fixes project deployment using new reserved DNS names. (#17872)

Security

• Disallow certain file names when uploading files to user's directory through web interface. (#18030)

6.8.4

Fixes

Usability

• Documentation generation for Julia extension packages can be generated correctly. (#17625)

• Free tier now takes deployment replicas into account. (#17803)

On-prem

Note: In the next minor release 6.9.0, the underlying JuliaHub deployment will change to using a Helm chart. This means that Helm chart only installations, without KOTS, can be used. But if an installation is going to stay using KOTS, there are some pre-requisites that are required to ensure that data is not lost as part of the upgrade to 6.9.0. As such, this 6.8.4 release is a required upgrade before upgrading to 6.9.0. If an installation is going to be upgraded using only the Helm chart and not KOTS in 6.9.0, then nothing is needed at this time.

6.8.3

Fixes

Usability

• Registered applications can start correctly. (#17659, TICKET-8103)

• Improved page load performance for users with SSO group membership exceeding 50 groups. (#17683, TICKET-8087)

• Audit event for project creation includes initial access metadata. (#17287, TICKET-7830)

• Correct group membership count is shown in User Management admin settings. (#16454, TICKET-7444)

Security

• Security authorization fix for package policies authorization. (#17751)

On-prem only

• Annotations added to help migrate to Helm chart usage. (#17707)

6.8.2

Fixes

Bug Fixes

• App launch from project table now launches application with access to JULIAHUB_PROJECT_UUID environmental variable (#17592)

• Time limit is correctly shown on Start Job dialog (#16038)

On-prem only

• Internal JuliaHub realm groups are always shown (#17454)

6.8.1

Fixes

Bug Fixes

• Prevent archived project deployment (#17391)

On-prem only

• If package sync migration fails during upgrade, upgrade process stops (#17217, TICKET-7841)

• Support artifact download within HTTP proxy environments (#17397, TICKET-7941)

• Package auth cache can invalidate correctly (#17310, TICKET-7852)

• Add login support for LDAP servers using older TLS ciphers (#17227, TICKET-7839)

6.8.0

New Features

• JuliaHub Project Github/Gitlab Import (#13779, #15481, #16330)
  • JuliaHub Projects can sync to and from an upstream Github or Gitlab repository

Enterprise Only

• Policy-based access controls for packages (#4789, #11502)

  • Only restriction by licenses is currently supported

• Overhaul of Registry Management (#9920, #16355, #16531)

  • Ability to share a private registry with specific users and groups

  • Integrates with new policy-based access controls

  • New UI for registries (#15798)

• Ability to register a package from a JuliaHub Project (#13763, #16642, #16712)

Improvements

Datasets

• Progress Bar on Dataset Upload (#2460)

• Prevent user from navigating away from page when upload is in progress (#16226)

• Ability to list datasets for project within RStudio Enterprise Only (#16497, #16781)

Projects

• Progress bar on file uploads to projects (#16150)

• Ability to clone a project that has been marked complete (#16246)

• Project launches do not share app instance with other projects (#16431, #16736)

• Improved usability by limiting a new project to one code resource and one dataset resource; existing projects prevented from adding more resources (#16580, #16675, #16776)

• After transfer succeeds, file listing is automatically updated (#16622)

Docs

• pkg.json generated for all versions in a registry (#16763, TICKET-7201)

Pluto

• Conversion of Jupyter notebooks to Pluto notebooks on upload (#8300, #16185)

Fixes

Performance

• Improved dataset listing view speed (#13884)

• Improved Audit events download speed (#15775, #16292)

Bug Fixes

• License metadata is preserved when adding datasets (#14044)

• Spaces are always allowed in project names (#15852)

• Project launch notification link connects to project folder correctly (#16229)

• Logo upload event shows in audit events (#16415)

• Audit event generated for when general access permission of a project is changed (#16804)

• Documentation generation can be turned off at the registry level (#16883, TICKET-7581)

• Documentation regeneration button is always visible (#17005, TICKET-7746)

6.7.4

• Fixed resetting project when adding additional resources

• Usability fixes for large projects

• Security fixes for projects ACLs

Enterprise

• Fixed issue loading JuliaHub within an airgap environment

6.7.3

• Bug fixes

v6.7.2

• Bug fixes

• Usability fixes for large projects

v6.7.1

• Bug fixes

v6.7.0

• New landing page: access your apps, projects and jobs much easier than before.

• Faster app & job launches

• Bug fixes

Enterprise

• Audit Event & Project collaboration bug fixes

v6.6.9

Onprem

• Bug fix for teamsrvr and pkgsrvr restarts

v6.6.8

• Bug fixes

v6.6.7

• Bug fixes

v6.6.5

• Bug fixes

v6.6.4

• Bug fixes

v6.6.3

• Bug fixes

v6.6.2

• Bug fixes

v6.6.1

• Genie app integration: Build data-centra applications from within JuliaHub using integrated Genie Builder with JuliaHub Projects.

  • This is only enabled on juliahub.com. For Enterprise installations, please contact JuliaHub Support.

• Refreshed Datasets UI

• Refreshed Projects list UI

• Julia updated to v1.10.4

• Bug fixes

Enterprise

• Dataset Import feature: enables ingesting datasets into JuliaHub from other data sources such as AWS S3 buckets

v6.5.4

• Sync fixes for on-premises installation

v6.5.3

• Bug fix for project creation from template

v6.5.2

• Bug fixes

• Julia IDE and julia batch versions use Julia 1.10

v6.5.1

• Bug fixes

• Cloudstation instance types are changed to only support the 8GB/vCPU option (r6i instance family) and V100 GPU option.

v6.5.0

• Project deployment enhancements:

  • Project deployments can be suspended and woken up using the drop down items in the "Deploy" button. This can also be configured to automatically suspend after a configured time. When a suspended project deployment receives a request, the deployment will be awaken up automaticallly. This allows users to save on compute costs.

  • Embed project deployments easily with embed codes that are generated under the "Deploy" button.

• Users can now revoke providers (Github etc.) authorization tokens from the preferences page.

• Removed extra login that occurs after connecting to a new app on juliahub.com.

• New Reader project role available to enable downloading and cloning of a project.

• Bug fixes

Enterprise

• Audit Events feature released.

v6.4.2

• Bug fixes

v6.4.1

• JuliaHub Projects can now be deployed as standalone WebApps on juliahub.com. The project owner will have the ability to make these WebApp deployments either public or restrict the access to only authorized users. Currently only Dash applications are supported for these WebApps.

• Developers can now resolve merge conflicts in their Projects using the "Manual merge" feature. This feature allows collaborators to edit the same project without worrying about conflicting modules.

• New users registering on JuliaHub now have to go through Google's reCaptcha before creating an account.

• Job details page now has a new UI with additional information, which means all job information (Metrics, Logs, machine spec, image information, etc) is now available in the same details page.

• Featured notebooks:- Admins can now pin public notebooks which are displayed in end-users Notebooks page as featured items. Featured notebooks can have custom thumbnail pictures which are then displayed in a notebook carousel.

• We have added a "Source" button on the package docs page which takes you to the package repository.

• We now display download stats for packages in our docs page, stats include total number of downloads that occurred in the past one month and a line graph plotted using daily downloads as data points.

• Notebooks landing page is now redesigned to show tags, owner and last modified date of all the notebooks in list view.

• We now show static notebook previews even for unevaluated notebooks and we now display a disclaimer for the HTML version of Pluto notebooks indicating that the static display is not interactive.

Enterprise

• Enterprise users can now register their own registries by using "My Registries" button in the packages page. The registry owner can also give other users access to download and potentially register packages in the private registry. Registry owners also get an option to fine tune the access control over their registries by restricting package registration to only authorized users.

• Clients can now disable full project cloning in their JuliaHub instance. Contact JuliaHub support for assistance.

• Package Analytics is now part of JuliaHub enterprise installs. Using this feature, for a given registry, an admin can now view

  • Number of packages present in each registry

  • Number of packages in use (Total number of packages that have at least one successful download request for a version)

  • Total number of successful package downloads

  • Numbers of users.

  • A table displaying top packages in use along with the number of users using that particular package. A toggle switch is provided to aggregate the package-use ignoring the versions.

  • Most active users (Along with Install Requests made by that particular user)

  • A graph which depicts package activities with respect to "Number of users of the packages" corresponding to "number of download requests"

• We now validate registry consistency whenever a registry is being created or updated. The following validations are done

  • Whether UUID and name are consistent with Package.toml

  • Existence of basic registry metadata in Registry.toml (name, UUID, packages section)

  • We make sure packages cannot have same name with different UUID

  • We also check whether the Registry name and Registry UUID is unique across all the available registries

  • We make sure packages don't have same UUID with different names across all the available registries

  • If a package is registered in multiple registries, then we check packages with the same UUID and name do not have version with conflicting hashes.

• Clients can now customize the landing page for their JuliaHub instance. Contact JuliaHub support for assistance.

Applications

• We now use separate VSCode extensions directories for every JuliaHub product, this ensures that a user installed VSCode extension for one app does not coincide with other apps.

• The Linux Desktop app now comes with VSCode preinstalled

• Following components have been updated in Julia IDE

  • Julia version has been updated to v1.9.3

  • Julia VSCode extension has been updated to v1.56.2

  • code-server has been updated to v4.18.0

• Code-Server stores users personal IDE settings in a JSON file, in the past, adding comments to this file would result in removal of all the customized settings because the resultant JSON file would be invalid, this issue has been fixed in the current version. End-User's can now have comments in their personal settings file.

• Projects can now be used in other apps. They are not limited to the Julia IDE.

• Quarto has been upgraded to v1.3.450

• rtools is now part of Windows Workstation app

• On Windows Workstation app, file extensions are now shown by default

v6.3.0

• v6.3.0 adds the capability to build a sysimage to go along with your job run. The sysimage is built before the job starts. After the sysimage build completes the sysimage is mounted to every Julia process the job utilizes (main and workers). JuliaHub users can choose to create a sysimage by checking the "Build SYSIMG" checkbox during job submission.

• We now have simple caching based on the pre-built sysimage. This feature ensures that additional runs of a job with the same manifest will reuse the already built sysimage.

• We're excited to introduce a fresh and modern user interface for JuliaHub. This update brings a host of usability improvements and a cleaner design, making user interactions smoother and ensures faster loading. UI improvements includes a major overhaul to Notifications, Registrator and Projects features.

• We have added a new grouping for shared datasets for easy distinction. Using these groupings, end-users can easily distinguish between shared datasets based on who shared them.

• Users can now create folders or directories in File explorer UI, this will help users to organize there files in an efficient way

• We now have a new search filter for dependencies & dependents in the packages UI, using this feature, end-users can now search for direct and indirect dependencies & dependents for a particular package.

• Users can now remove a project viewer's access by setting the resource's general access level to "No Access"

Enterprise

• Job time limits can now be made optional by an admin on enterprise installs, if this option is enabled, end-users on the JuliaHub instance can start jobs with no time limits.

Applications

• Julia version has been updated to v1.9.2 in Julia IDE and batch jobs

• We have added following R packages to WindowsWorkstation app:- ggplot, ggPMX, xpose, xpose4 and vpc

• Users can now access JuliaHub Datasets through R

• Users can now install TinyTex packages, and all the newly installed TinyTex packages will automatically go to persistent storage, hence, these packages can be loaded across the sessions without installing them again.

v6.2.1

• JuliaHub users can now extend the job time limit directly from the job details page

• We now allow elastic distributed workloads on JuliaHub. Users get a choice to opt in for elastic cluster mode via job submission UI, jobs started with elastic cluster mode enabled will benefit from quick start times, resiliency to failures, and ability to dynamically (programmatically) scale jobs up or down.

• We have redesigned the JuliaHub UI for better accessibility of all the features and resources.

• ChatGPT integration with JuliaHub:- Users can now ask questions about Julia and Julia packages in a natural language, these questions are answered by ChatGPT, with context provided via existing documentation.

• Pressing "/" in JuliaHub page; automatically passes control to search functionality, users don't have to manually click on the search box, they can press "/" and start typing the search query.

• Registrator now supports bulk package registrations. End-user's can register more than one package at a time, this is useful in scenarios where the 2 or more new packages that are about to be registered are interdependent.

• While creating a Project, end-users now get a choice to select editing "Workflow", as of now, there are 2 modes: "Concurrent editing" and "Exclusive editing". Concurrent editing lets multiple contributors work on a project at the same time, combining their changes when they're ready. In an exclusive editing workflow, the ability to modify files in the project is delegated to one contributor at a time.

• We now show package synchronization status to non-admin users (Enterprise mode only)

• We now show the registry that contains the package alongside with package description in JuliaHub docs page, this is helpful to enterprise customers who have multiple registries setup on their JuliaHub instance.

Applications

• We have updated Pluto version to v0.19.26

• We have removed all restrictions on user defined ENV variables (However, we do warn if your ENV is not POSIX.1 compliant)

• Quarto is now available on JuliaHub as a commandline tool (Quarto VS-Code extension is not available at the moment)

• JuliaHub now uses a dedicated JULIA_HOME for each IDE app

• Improved interoperability across multiple versions of code-server.

v6.1.0

• JuliaHub Projects: We're excited to introduce the JuliaHub Projects, a powerful new feature that allows you to encapsulate files, folders, datasets, code, and share permissions, all within JuliaHub. Collaborate and share your work with your team members with ease. Learn more about this feature by visiting https://juliahub.com/company/resources/webinar/improving-julia-collaboration/.

• BlobTree Viewer: We've added a new Dataset Viewer feature that enables you to view the BlobTree. The BlobTree is an important data structure in JuliaHub that represents datasets as hierarchical blobs. To learn more about the BlobTree Viewer, please visit https://docs.juliahub.com/DataSets/4adr3/0.2.8/reference/#DataSets.BlobTree.

Enterprise

• Event Auditing: You can now view JuliaHub events for auditing purposes. Keep track of all the changes happening within your enterprise account with this new feature.

• Search Filter: We've added the ability to filter search results by multiple registries, making it easier to find the packages you need.

• Repository Metadata Display: The metadata for Bitbucket packages is now displayed, making it easier to get the information you need about your repositories.

Applications

• Gitlens Extension: We've added the Gitlens extension to the Julia IDE, enhancing your experience when working with Git repositories.

• Julia Version Upgrade: We've upgraded the Julia version to 1.8.5, offering improved performance and stability.

• User environment variables: Applications can load environment variables defined in the user's bashrc file.

v6.0.2

• Provide free access to a 2VCPU, 16GB RAM machine for up to 20 hours per month

• Bug fixes

v6.0.1

• Bug fixes

v6.0.0

• Users can add/view/edit their files without opening any app

• New and improved Pluto home page

• Automatic static export will now be available every time a notebook completes the execution loop

• Ability to edit or run Pluto HTML notebooks with single click

• Ability to create notebooks from a Pluto app

• Ability to view a dataset

• Ability to upload/download multiple versions of a dataset

• Ability to manage jobs/apps from the home page

• Bug fixes

Enterprise Version

• Ability to re-run jobs (experimental)

Applications

• Download/upload support added for Windows Workstation

• Allow setting JULIA environment variables

• Upgrade JuliaHub Extension to v0.6.9

• Upgrade Julia IDE (CodeServer) to 4.8.2

• Added utility programs like zip, gh

v5.8.5

• Bug fixes

v5.8.4

• Bug fixes

v5.8.2

• Improved landing page

• Bug fixes

v5.8.1

• Bug fixes

v5.8.0

• Official Julia binaries are now hosted

• Streamlined application startup experience

Enterprise

• Users can configure custom domain prefix for apps

• New Application: Windows Workstation

• Admins can configure multiple versions for job images

• Bug fixes

v5.7.4

• Bug fixes

v5.7.2

• Bug fixes

v5.7.1

• Bug fixes

v5.7.0

• CPU and Memory usage of jobs are now available as charts

• Bug fixes

Enterprise

• Offline package server

• New application: Windows Desktop

• New feature: Projects (Experimental)

v5.6.1

• Bug fixes

v5.6.0

• Added links to PkgEval reports

• Bug fixes

Enterprise

• Automatic package registration for Bitbucket server

• Support for multiple private registries

• Support for SSH protocol during package registration

• UI to trigger package documentation generation

• UI to view synchronization failures with pkg.juliahub.com

• UI to disable package versions in registry

• Support for SSL Offloading

• UI to toggle PkgServer authentication

• K8s based installation/deployment is managed using Replicated

v5.5.2

• Upgrade DocumentationGenerator to v0.4.7

• Bug fixes

v5.5.1

• AWS Credential configuration is now optional

• Jobs: Julia version updated to v1.6.5

• Jobs: Pluto updated to v0.17.7

• Bug fixes

v5.5.0

• App, job images configurable via UI

• Ability to configure Job limit per user

• Configurable session timeout for Application

• Endpoint to give package server status

• Sessions are now stored in the server instead of cookies

• Package Stats for General registry

• Option to limit container memory usage

• Captcha added while adding credit cards

• New User role: customer-admin

• New dashboard for total monthly payments

• Ability to view all datasets across all users

• Bug fixes

v5.4.0

• Support datasets sharing for LDAP users

• New subdomain for package docs. For eg: https://docs.juliahub.com/PostgresORM/QI2db/0.1.6/ instead of https://juliahub.com/docs/PostgresORM/QI2db/0.1.6/

• JuliaHub tutorials are now hosted at help.juliahub.com instead of docs.juliahub.com

• Introducing JuliaSim IDE app

• Support for SSL Offloading

• Static CSRF protection for JuliaHub APIs

• Admin UI to toggle PkgServer authentication

• Admin UI to configure authorization

• Cross container requests are now encrypted

• Session cookies are now compressed and chunked.

• Support for PNG, JPEG company logos

• Add support for dataset owners and updates

• Jobs: Automated ssh-key generation for easier git integration

• Add tmux to CodeServer

• Improved Pluto notebooks

• Jobs: ability to set log levels

• Integrate freshdesk support widget

• App domains don't need re-authentication in Enterprise version