| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| README.md | 2026-07-17 | 5.2 kB | |
| v6.1.0 source code.tar.gz | 2026-07-17 | 95.2 MB | |
| v6.1.0 source code.zip | 2026-07-17 | 96.4 MB | |
| Totals: 3 Items | 191.6 MB | 0 | |
MAGDA v6.1.0 is the official production release containing the changes merged since v6.0.0.
Highlights
New mgd command-line interface
This is the first official MAGDA release to include @magda/mgd, an npm-installable CLI for working with MAGDA catalogs from a terminal or coding agent.
- Authenticate with API keys and named profiles, including environment-variable overrides and profile create, update, select and remove commands.
- Search datasets using keyword or semantic search, and inspect complete dataset and distribution records including custom aspects.
- Create and update datasets and distributions, add or replace files, remove distributions, and transfer large files with resumable multipart uploads and HTTP Range downloads.
- Create, read, replace, partially merge and safely delete custom aspect definitions and values.
- Publish or unpublish datasets with transactional distribution cascading, or manage individual distributions.
- Maintain dataset and distribution version history from high-level mutation commands.
- Produce consistent machine-readable JSON output and fall back to raw MAGDA API requests when needed.
- Install bundled coding-agent skills for Claude Code, Codex and opencode, with guided setup and dataset-management workflows.
mgd requires Node.js 22 or later. Install the CLI with:
:::console
npm install --global @magda/mgd@6.1.0
For complete setup and usage instructions—including copy-ready guided installation prompts for Claude Code, Codex and opencode—see the mgd CLI user guide.
Related pull requests: #3683, #3695, #3697, #3698, #3700, #3701, #3705, #3709, #3716, #3720 and #3722.
Resumable large-file storage
storage-api now supports resumable multi-GB transfers without buffering an entire file or increasing the ingress body-size limit:
- S3 multipart upload proxy endpoints for initiating an upload, uploading and listing parts, completing an upload, and aborting an upload.
- HTTP Range downloads with
206 Partial Contentand resume support. - Signed, expiring upload tokens and configurable part-size and incomplete-upload lifecycle settings.
- A corrected create-bucket route at
/v0/storage/buckets/{bucketId}.
Registry and authorization
- Added
DELETE /v0/registry/aspects/{id}for safely deleting unused tenant-scoped aspect definitions. Deletion is rejected with409 Conflictwhile records still reference the aspect. See #3699. - Fixed
DELETE /api/v0/auth/users/:userId, which previously generated invalid SQL and could not delete users. See #3708. - Reorganised the generated Registry API documentation so bulk multi-record aspect operations are grouped with the other record-service operations. This is a documentation-only change. See #3707.
Distribution version tracking
The web client now advances a distribution's version when its metadata is edited, aligning its record-version handling with mgd. Version-history arithmetic is also robust to non-contiguous histories created by another writer. See #3721.
Semantic search and deployment tooling
- Fixed semantic indexer crash loops caused by an invalid combination of vector
compressionLevelandencodersettings. - Updated the CSV semantic-indexer chart dependency and added a clear Helm minimum-version guard.
- Updated CI and downstream builder images to Helm 3.17.4 so development and release deployments satisfy the new requirement.
Developer tooling and packaging
- Updated
ts-module-alias-transformerto restore declaration-file alias rewriting and prevent silently incomplete builds. See #3684. - Expanded documentation for MAGDA API documentation generation and publishing, and for
mgdauthentication and coding-agent workflows.
Upgrade notes
- MAGDA v6.1.0 requires Helm 3.17 or later when rendering
magda-core. The release builder and downstream deployment images use Helm 3.17.4. - Clients creating storage buckets should use the documented
/v0/storage/buckets/{bucketId}route.
Full change set
See the complete comparison: v6.0.0...v6.1.0.