feat!: rename package from PURL.jl to PackageURL.jl

BREAKING CHANGE: Module and type names have changed
- Module: PURL → PackageURL
- Type: PackageURL → PURL (avoids module/type collision)

Migration:
  using PURL                    → using PackageURL
  parse(PackageURL, s)          → parse(PURL, s)
  PackageURL("npm", ...)        → PURL("npm", ...)

This rename satisfies Julia General Registry AutoMerge requirements
(minimum 5 characters, proper CamelCase) and aligns with the PURL
ecosystem naming convention (packageurl-python, packageurl-js, etc.).

Author: s-celles

.github/workflows/Documentation.yml

@@ -47,6 +47,6 @@ jobs:
         shell: julia --project=docs --color=yes {0}
         run: |
           using Documenter: DocMeta, doctest
-          using PURL
-          DocMeta.setdocmeta!(PURL, :DocTestSetup, :(using PURL); recursive=true)
-          doctest(PURL)
+          using PackageURL
+          DocMeta.setdocmeta!(PackageURL, :DocTestSetup, :(using PackageURL); recursive=true)
+          doctest(PackageURL)

CHANGELOG.md

@@ -1,45 +1,63 @@
 # Changelog
 
-All notable changes to PURL.jl will be documented in this file.
+All notable changes to PackageURL.jl will be documented in this file.
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ## [Unreleased]
 
+## [0.4.0] - 2026-02-04
+
+### Changed
+
+- **BREAKING**: Renamed package from `PURL.jl` to `PackageURL.jl` for Julia General Registry compliance
+- **BREAKING**: Renamed module from `PURL` to `PackageURL`
+- **BREAKING**: Renamed struct from `PackageURL` to `PURL` to avoid module/type naming collision
+
+### Migration Guide
+
+To migrate from PURL.jl (pre-1.0) to PackageURL.jl (1.0+):
+
+```julia
+# Before (PURL.jl)
+using PURL
+purl = parse(PackageURL, "pkg:npm/lodash@4.17.21")
+purl = PackageURL("npm", nothing, "lodash", "4.17.21", nothing, nothing)
+
+# After (PackageURL.jl)
+using PackageURL
+purl = parse(PURL, "pkg:npm/lodash@4.17.21")
+purl = PURL("npm", nothing, "lodash", "4.17.21", nothing, nothing)
+```
+
+Summary of changes:
+1. Change `using PURL` to `using PackageURL`
+2. Change `parse(PackageURL, ...)` to `parse(PURL, ...)`
+3. Change `tryparse(PackageURL, ...)` to `tryparse(PURL, ...)`
+4. Change `PackageURL(...)` constructor to `PURL(...)`
+
 ### Added
-- Initial implementation of PURL.jl
-- `PackageURL` struct for representing Package URLs
+- Initial implementation of PackageURL.jl
+- `PURL` struct for representing Package URLs
 - `PURLError` exception type for parsing and validation errors
-- `parse(PackageURL, s)` for parsing PURL strings
-- `tryparse(PackageURL, s)` for safe parsing
+- `parse(PURL, s)` for parsing PURL strings
+- `tryparse(PURL, s)` for safe parsing
 - `string(purl)` for serializing to canonical PURL format
 - `purl"..."` string macro for compile-time validated literals
 - Support for all PURL components: type, namespace, name, version, qualifiers, subpath
 - Percent encoding/decoding per PURL specification
 - Type-specific validation rules for Julia, npm, PyPI ecosystems
 - Official PURL test suite integration
 - Comprehensive documentation with Documenter.jl
-- Bundle official purl-spec v1.0.0 as Julia artifact with all 35 type definitions
+- Bundle official purl-spec v0.4.0 as Julia artifact with all 35 type definitions
 - `purl_spec_path()`, `type_definitions_path()`, `test_fixtures_path()` functions for accessing bundled files
 - `load_bundled_type_definitions!()` for loading official type definitions (called automatically on module load)
 
-### Changed
-- Nothing yet
-
-### Deprecated
-- Nothing yet
-
-### Removed
-- Nothing yet
-
 ### Fixed
 - Julia UUID validation now strictly validates RFC 4122 format (8-4-4-4-12 hex digits with hyphens)
 - NuGet package names are now correctly normalized to lowercase for PURL canonical form
 
-### Security
-- Nothing yet
-
 ## [0.1.0] - Unreleased
 
 ### Added
@@ -49,5 +67,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Serialize PURLs to canonical string format
 - String macro for PURL literals
 
-[Unreleased]: https://github.com/JuliaLang/PURL.jl/compare/v0.1.0...HEAD
-[0.1.0]: https://github.com/JuliaLang/PURL.jl/releases/tag/v0.1.0
+[Unreleased]: https://github.com/s-celles/PackageURL.jl/compare/v0.4.0...HEAD
+[0.4.0]: https://github.com/s-celles/PackageURL.jl/compare/v0.1.0...v0.4.0
+[0.1.0]: https://github.com/s-celles/PackageURL.jl/releases/tag/v0.1.0

CONTRIBUTING.md

@@ -1,6 +1,6 @@
-# Contributing to PURL.jl
+# Contributing to PackageURL.jl
 
-Thank you for your interest in contributing to PURL.jl! This document provides guidelines and information for contributors.
+Thank you for your interest in contributing to PackageURL.jl! This document provides guidelines and information for contributors.
 
 ## Getting Started
 
@@ -13,8 +13,8 @@ Thank you for your interest in contributing to PURL.jl! This document provides g
 
 1. Clone the repository:
    ```bash
-   git clone https://github.com/s-celles/PURL.jl.git
-   cd PURL.jl
+   git clone https://github.com/s-celles/PackageURL.jl.git
+   cd PackageURL.jl
    ```
 
 2. Start Julia with the project:
@@ -132,10 +132,10 @@ end
 ## Project Structure
 
 ```
-PURL.jl/
+PackageURL.jl/
 ├── src/
-│   ├── PURL.jl          # Main module
-│   ├── types.jl         # Core types (PackageURL, PURLError)
+│   ├── PackageURL.jl    # Main module
+│   ├── types.jl         # Core types (PURL, PURLError)
 │   ├── parse.jl         # Parsing implementation
 │   ├── serialize.jl     # String conversion
 │   ├── encoding.jl      # Percent encoding/decoding
@@ -154,7 +154,7 @@ PURL.jl/
 
 ## Type Definition Maintenance
 
-PURL.jl uses official type definitions from the [purl-spec](https://github.com/package-url/purl-spec) repository. These definitions follow the ECMA-427 schema.
+PackageURL.jl uses official type definitions from the [purl-spec](https://github.com/package-url/purl-spec) repository. These definitions follow the ECMA-427 schema.
 
 ### Updating Type Definitions
 
@@ -183,7 +183,7 @@ When new types are added to purl-spec:
 
 3. Verify the type loads correctly:
    ```julia
-   using PURL
+   using PackageURL
    def = load_type_definition("data/type_definitions/newtype.json")
    ```
 
@@ -225,7 +225,7 @@ The Julia PURL type was added via [purl-spec#540](https://github.com/package-url
 Example Julia PURLs:
 ```
 pkg:julia/Dates@1.9.0?uuid=ade2ca70-3891-5945-98fb-dc099432e06a
-pkg:julia/PURL@0.1.0?uuid=c2271b70-7219-4bda-bcc3-62ec08ead5b7
+pkg:julia/PackageURL@0.4.0?uuid=c2271b70-7219-4bda-bcc3-62ec08ead5b7
 ```
 
 ## Adding Support for New PURL Types
@@ -283,4 +283,4 @@ julia --project=docs -e 'using Pkg; Pkg.instantiate(); include("docs/make.jl")'
 
 ## License
 
-By contributing to PURL.jl, you agree that your contributions will be licensed under the MIT License.
+By contributing to PackageURL.jl, you agree that your contributions will be licensed under the MIT License.

Project.toml

@@ -1,7 +1,7 @@
-name = "PURL"
+name = "PackageURL"
 uuid = "c2271b70-7219-4bda-bcc3-62ec08ead5b7"
-version = "0.3.2"
-authors = ["PURL.jl Contributors"]
+version = "0.4.0"
+authors = ["PackageURL.jl Contributors"]
 
 [deps]
 JSON3 = "0f8b85d8-7281-11e9-16c2-39a750bddbf1"

README.md

@@ -1,30 +1,29 @@
-# PURL.jl
+# PackageURL.jl
 
-[![Build Status](https://github.com/s-celles/PURL.jl/actions/workflows/CI.yml/badge.svg)](https://github.com/s-celles/PURL.jl/actions/workflows/CI.yml)
-[![Documentation](https://img.shields.io/badge/docs-dev-blue.svg)](https://s-celles.github.io/PURL.jl/dev)
-[![Coverage](https://codecov.io/gh/s-celles/PURL.jl/branch/main/graph/badge.svg)](https://codecov.io/gh/s-celles/PURL.jl)
+[![Build Status](https://github.com/s-celles/PackageURL.jl/actions/workflows/CI.yml/badge.svg)](https://github.com/s-celles/PackageURL.jl/actions/workflows/CI.yml)
+[![Documentation](https://img.shields.io/badge/docs-dev-blue.svg)](https://s-celles.github.io/PackageURL.jl/dev)
+[![Coverage](https://codecov.io/gh/s-celles/PackageURL.jl/branch/main/graph/badge.svg)](https://codecov.io/gh/s-celles/PackageURL.jl)
 
 A pure-Julia implementation of the [Package URL (PURL)](https://github.com/package-url/purl-spec) specification ([ECMA-427](https://www.ecma-international.org/publications-and-standards/standards/ecma-427/)).
 
-**[Documentation](https://s-celles.github.io/PURL.jl/dev)** | **[API Reference](https://s-celles.github.io/PURL.jl/dev/api/)**
+**[Documentation](https://s-celles.github.io/PackageURL.jl/dev)** | **[API Reference](https://s-celles.github.io/PackageURL.jl/dev/api/)**
 
 ## Installation
 
 ```julia
 using Pkg
-Pkg.add(url="https://github.com/s-celles/PURL.jl")  # until unregistered
-# Pkg.add("PURL")  # when registered to General registry
+Pkg.add("PackageURL")
 ```
 
 The package includes all 35 official PURL type definitions from [purl-spec v1.0.0](https://github.com/package-url/purl-spec/releases/tag/v1.0.0), bundled as a Julia artifact. Type definitions are automatically loaded when you first use the package.
 
 ## Quick Start
 
 ```julia
-using PURL
+using PackageURL
 
 # Parse a PURL string
-purl = parse(PackageURL, "pkg:npm/lodash@4.17.21")
+purl = parse(PURL, "pkg:npm/lodash@4.17.21")
 purl.type      # "npm"
 purl.name      # "lodash"
 purl.version   # "4.17.21"
@@ -36,7 +35,7 @@ purl = purl"pkg:pypi/requests@2.28.0"
 string(purl)  # "pkg:pypi/requests@2.28.0"
 ```
 
-See the [documentation](https://s-celles.github.io/PURL.jl/dev) for PURL components, ecosystem examples, and API reference.
+See the [documentation](https://s-celles.github.io/PackageURL.jl/dev) for PURL components, ecosystem examples, and API reference.
 
 ## License
 

ROADMAP.md

@@ -1,10 +1,10 @@
-# PURL.jl Roadmap
+# PackageURL.jl Roadmap
 
-This document outlines the development status and future plans for PURL.jl.
+This document outlines the development status and future plans for PackageURL.jl.
 
 ## Current Status
 
-PURL.jl aims for full compliance with ECMA-427 (1st edition, December 2025). The implementation passes the official purl-spec test suite and correctly handles the core PURL format.
+PackageURL.jl aims for full compliance with ECMA-427 (1st edition, December 2025). The implementation passes the official purl-spec test suite and correctly handles the core PURL format.
 
 ### ECMA-427 Compliance Status
 
@@ -17,7 +17,7 @@ PURL.jl aims for full compliance with ECMA-427 (1st edition, December 2025). The
 | 5.6.3 | Encode namespace segments individually | Implemented |
 | 6 | Type Definition Schema Support | Implemented |
 
-**Note:** Full compliance verification is pending for v0.4.0 release.
+**Note:** Full compliance verification is pending for v0.5.0 release.
 
 ### Completed Features
 
@@ -49,46 +49,43 @@ Additional types can be added via JSON type definitions without code changes.
 
 ## Version History
 
-### v0.2.0 - Full ECMA-427 Compliance ✓
-- [x] Fix scheme slash handling
-- [x] Fix type character validation
-- [x] Fix colon encoding
-- [x] Fix empty qualifier handling
-- [x] Fix namespace segment encoding
-- [x] Add compliance test cases
+### v0.4.0 - Package Rename and Initial Release ✓
+- [x] Renamed package from PURL.jl to PackageURL.jl for Julia General Registry compliance
+- [x] Renamed module from PURL to PackageURL
+- [x] Renamed struct from PackageURL to PURL (to avoid module/type collision)
+- [x] Full ECMA-427 compliance
+- [x] All 35 official type definitions bundled
+
+### v0.3.2 - Official Type Test Coverage ✓
+- [x] All 37 official purl-spec type definitions verified to load correctly
+- [x] Normalization derivation tests
+- [x] Qualifier extraction tests
+- [x] JSONSchema validation against official purl-type-definition schema
+
+### v0.3.1 - Official Type Definition Format Support ✓
+- [x] Support official ECMA-427 type definition schema format from purl-spec repository
 
 ### v0.3.0 - Extended Type Support ✓
 - [x] Add maven type rules
 - [x] Add nuget type rules
 - [x] Add golang type rules
 - [x] JSON-based type definition loading (Feature 007)
 
-### v0.3.1 - Official Type Definition Format Support ✓
-- [x] Support official ECMA-427 type definition schema format from purl-spec repository
-  - Parse `name_definition.case_sensitive` → lowercase normalization
-  - Parse `name_definition.normalization_rules` text patterns
-  - Parse `qualifiers_definition` array format
-- [x] Test against official purl-spec type definitions (cargo, pypi, npm, maven, etc.)
-
-### v0.3.2 - Official Type Test Coverage ✓
-- [x] All 37 official purl-spec type definitions verified to load correctly
-- [x] Normalization derivation tests:
-  - 15 lowercase types verified (alpm, apk, bitbucket, bitnami, composer, deb, github, golang, hex, luarocks, npm, oci, otp, pub, pypi)
-  - 22 case-sensitive types verified (bazel, cargo, cocoapods, conan, conda, cpan, cran, docker, gem, generic, hackage, huggingface, julia, maven, mlflow, nuget, opam, qpkg, rpm, swid, swift, yocto)
-  - pypi underscore replacement verified
-- [x] Qualifier extraction tests (maven, pypi, julia, swid)
-- [x] JSONSchema validation against official purl-type-definition schema
-  - 34 types pass schema validation
-  - 3 types have upstream schema issues (bazel, julia, yocto) - see UPSTREAM-ISSUES.md
-- [x] CONTRIBUTING.md with type definition maintenance guide
+### v0.2.0 - Full ECMA-427 Compliance ✓
+- [x] Fix scheme slash handling
+- [x] Fix type character validation
+- [x] Fix colon encoding
+- [x] Fix empty qualifier handling
+- [x] Fix namespace segment encoding
+- [x] Add compliance test cases
 
 ---
 
 ## Upcoming
 
-### v0.4.0 - Release Candidate
-- [ ] Complete documentation
-- [ ] API documentation review
+### v0.5.0 - Post-Release Improvements
+- [ ] Complete documentation review
+- [ ] API documentation audit
 - [ ] Performance optimization if needed
 - [ ] Final test coverage review