feat(maven): Add Maven registry protocol support (storage, auth, routing, interfaces, and exports)
This commit is contained in:
12
changelog.md
12
changelog.md
@@ -1,5 +1,17 @@
|
||||
# Changelog
|
||||
|
||||
## 2025-11-21 - 1.2.0 - feat(maven)
|
||||
Add Maven registry protocol support (storage, auth, routing, interfaces, and exports)
|
||||
|
||||
- Add Maven protocol to core types (TRegistryProtocol) and IRegistryConfig
|
||||
- SmartRegistry: initialize Maven registry when enabled, route requests to /maven, and expose it via getRegistry
|
||||
- RegistryStorage: implement Maven storage helpers (get/put/delete artifact, metadata, list versions) and path helpers
|
||||
- AuthManager: add UUID token creation/validation/revocation for Maven and integrate into unified validateToken/authorize flow
|
||||
- New ts/maven module: exports, interfaces and helpers for Maven coordinates, metadata, and search results
|
||||
- Add basic Cargo (crates.io) scaffolding: ts/cargo exports and Cargo interfaces
|
||||
- Update top-level ts/index.ts and package exports to include Maven (and cargo) modules
|
||||
- Tests/helpers updated to enable Maven in test registry and add Maven artifact/checksum helpers
|
||||
|
||||
## 2025-11-20 - 1.1.1 - fix(oci)
|
||||
Improve OCI manifest permission response and tag handling: include WWW-Authenticate header on unauthorized manifest GETs, accept optional headers in manifest lookup, and persist tags as a unified tags.json mapping when pushing manifests.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user