public_suffix 7.0.1 → 7.0.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 96c64092cb38c0249d59c8ab4193438275155f8871affda9eb141cdd8bce1d0c
-  data.tar.gz: 1d3c97ee5f787e0bc69c2552b9e6ff587e3a2d0a7e4ddd91b1be652173f03269
+  metadata.gz: 1ff61cb9451fff6aed47766db53c40c7a4888805c3c7bc5f6c6589d47504345c
+  data.tar.gz: e70fb4d7e20fce2a5e3fd89b30e4007c538fcaeba58171b6d931819c86d95687
 SHA512:
-  metadata.gz: 2ddedb44078dd0e2d3c2d15f25021fdd0bfe251fd2507cfba82dee37b6a67a4ce0adeecf6f0c884930d05c0faae02550c9cfe15ac3f616f8fd2561973c5124cd
-  data.tar.gz: 729bc2bb98203d65555b9e1aedd62f402f809186aefea93077b9c648b0c68a6587206697f76c8e31299ffa2d207f823794241840c1f3805cee32b461c3a9d11d
+  metadata.gz: ec5527af0c8aaef6707cd43e4ac1aea2d7fecffb0b1d1db2c12798fba1e052750a50ffc808d9fd4ee0176b880f548fe574d2030f00acd7a66cc2a7bd53a452ee
+  data.tar.gz: 709c40dc8fb9661ebde8e5c3c7e0226089ea3390aefef01faae733c905362c7be665aeaea1a1438e9b6f7f003c02dda4b9ebc5a612fc470bdd00a6f84f35fdda

data/CHANGELOG.md

@@ -1,6 +1,16 @@
 # Changelog
 
 
+## Unreleased
+
+
+## 7.0.2 - 2026-01-04
+
+### Changed
+
+- Excluded symlinks and unnecessary files from gem packaging. On Windows symlinks cannot be created without Administrator privileges or with developer mode enabled #496.
+
+
 ## 7.0.1 - 2026-01-03
 
 ### Changed

data/lib/public_suffix/version.rb

@@ -9,6 +9,6 @@
 module PublicSuffix
 
   # @return [String] the current library version
-  VERSION = "7.0.1"
+  VERSION = "7.0.2"
 
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: public_suffix
 version: !ruby/object:Gem::Version
-  version: 7.0.1
+  version: 7.0.2
 platform: ruby
 authors:
 - Simone Carletti
@@ -19,13 +19,9 @@ extra_rdoc_files:
 - LICENSE.txt
 files:
 - ".yardopts"
-- AGENTS.md
 - CHANGELOG.md
-- CLAUDE.md
-- CONTRIBUTING.md
 - LICENSE.txt
 - README.md
-- RELEASING.md
 - SECURITY.md
 - data/list.txt
 - lib/public_suffix.rb
@@ -40,9 +36,9 @@ licenses:
 metadata:
   bug_tracker_uri: https://github.com/weppos/publicsuffix-ruby/issues
   changelog_uri: https://github.com/weppos/publicsuffix-ruby/blob/master/CHANGELOG.md
-  documentation_uri: https://rubydoc.info/gems/public_suffix/7.0.1
+  documentation_uri: https://rubydoc.info/gems/public_suffix/7.0.2
   homepage_uri: https://simonecarletti.com/code/publicsuffix-ruby
-  source_code_uri: https://github.com/weppos/publicsuffix-ruby/tree/v7.0.1
+  source_code_uri: https://github.com/weppos/publicsuffix-ruby/tree/v7.0.2
   funding_uri: https://github.com/sponsors/weppos
 rdoc_options: []
 require_paths:

data/AGENTS.md

@@ -1,38 +0,0 @@
-# Agent Instructions
-
-Instructions for AI coding agents when working on this project.
-
-## Agent Organization
-
-When creating agent instruction files:
-
-- The main file should always be named `AGENTS.md`
-- Create a `CLAUDE.md` symlink pointing to `AGENTS.md` for compatibility with Claude Code
-
-## Project Overview
-
-PublicSuffix for Ruby is a Ruby domain name parser based on the Public Suffix List. It provides domain parsing, validation, and extraction with support for private domains, FQDN handling, and custom rule definitions.
-
-## Key Documentation
-
-- **[README.md](README.md)** - Library overview, features, usage examples, and API reference
-- **[CONTRIBUTING.md](CONTRIBUTING.md)** - Contribution guidelines, commit format, testing approach
-- **[Public Suffix List](https://publicsuffix.org/)** - Official Public Suffix List documentation
-- **[RubyDoc](https://rubydoc.info/gems/public_suffix)** - API documentation
-
-## Project-Specific Context
-
-### Code Style Notes
-
-- Use Conventional Commits format (see [CONTRIBUTING.md](CONTRIBUTING.md#commit-message-guidelines))
-- Follow Ruby community style guidelines
-- Do not include AI attribution in commit messages or code comments
-- Tests are mandatory for all changes
-
-## Project Structure
-
-```
-lib/public_suffix/      # Main library code
-test/                   # Test suite
-data/                   # Public Suffix List data
-```

data/CLAUDE.md

@@ -1 +0,0 @@
-AGENTS.md

data/CONTRIBUTING.md

@@ -1,129 +0,0 @@
-# Contributing to PublicSuffix for Ruby
-
-Thank you for your interest in contributing to PublicSuffix for Ruby!
-
-## Development Workflow
-
-1. Fork and clone the repository
-2. Install dependencies: `bundle install`
-3. Create a branch: `git checkout -b feature/your-feature`
-4. Make your changes
-5. Run tests: `rake test`
-6. Commit using Conventional Commits format (see below)
-7. Push and create a pull request
-
-## Commit Message Guidelines
-
-We follow the [Conventional Commits](https://www.conventionalcommits.org/) specification for commit messages.
-
-We follow the [Common Changelog](https://common-changelog.org/) format for changelog entries.
-
-### Format
-
-```
-<type>(<scope>): <subject>
-
-<body>
-
-<footer>
-```
-
-Use lowercase for `<type>`. Capitalize the first letter of `<subject>` (sentence-style). See examples below.
-
-### Type
-
-- **feat**: A new feature
-- **fix**: A bug fix
-- **chore**: Other changes that don't modify src or test files
-- **docs**: Documentation only changes
-- **style**: Code style changes (formatting, etc.)
-- **refactor**: Code change that neither fixes a bug nor adds a feature
-- **perf**: Performance improvement
-- **test**: Adding or updating tests
-- **build**: Changes to build system or external dependencies
-- **ci**: Changes to CI configuration files and scripts
-
-### Scope
-
-- **parser**: List parsing and rule handling
-- **domain**: Domain parsing and validation
-- **list**: List management and operations
-- **rule**: Rule definitions and matching
-
-### Examples
-
-```bash
-feat(parser): Add support for wildcard exceptions
-
-fix(domain): Handle FQDN trailing dots correctly
-
-docs: Update usage examples in README
-
-refactor(list): Simplify rule lookup logic
-```
-
-### Breaking Changes
-
-Add `BREAKING CHANGE:` in the footer:
-
-```
-feat(domain): Change parse return type
-
-BREAKING CHANGE: Domain#parse now returns nil for invalid domains instead of raising.
-Update code to check for nil returns.
-```
-
-## Testing
-
-### Running Tests
-
-```bash
-rake test                        # Run all tests
-rake test TEST=test/domain_test.rb  # Run specific test file
-```
-
-### Writing Tests
-
-- Tests use Minitest framework
-- Place tests in `test/` directory
-- Use descriptive test names
-- Test both happy paths and error cases
-- Include tests for edge cases (empty strings, unicode, etc.)
-
-## Pull Request Process
-
-1. Update documentation for API changes
-2. Add tests for new features or bug fixes
-3. Ensure all tests pass: `rake test`
-4. Use Conventional Commits format
-5. Provide clear PR description with context
-6. Reference related issues if applicable
-
-## Code Style
-
-- Follow [Ruby Style Guide](https://rubystyle.guide/)
-- Use RuboCop configuration if present
-- Add YARD documentation for public methods
-- Keep methods focused and small
-
-### Ruby-Specific Guidelines
-
-- Follow idiomatic Ruby patterns
-- Use meaningful variable and method names
-- Prefer `raise` over `fail`
-- Use blocks and iterators effectively
-- Follow the principle of least surprise
-- Prefer methods that return values over side effects
-
-### Documentation
-
-- Add YARD comments for public methods
-- Include usage examples in documentation
-- Update README.md for user-facing changes
-- Keep inline comments minimal - prefer self-documenting code
-
-## Questions?
-
-Open an issue for questions, feature discussions, or bug reports.
-
-Thank you for contributing!

data/RELEASING.md

@@ -1,96 +0,0 @@
-# Releasing
-
-This document describes the steps to release a new version of PublicSuffix.
-
-## Prerequisites
-
-- You have commit access to the repository
-- You have push access to the repository
-- You have a GPG key configured for signing tags
-- You have permission to publish to RubyGems
-
-## Release process
-
-1. **Determine the new version** using [Semantic Versioning](https://semver.org/)
-
-   ```shell
-   VERSION=X.Y.Z
-   ```
-
-   - **MAJOR** version for incompatible API changes
-   - **MINOR** version for backwards-compatible functionality additions
-   - **PATCH** version for backwards-compatible bug fixes
-
-2. **Update the version file** with the new version
-
-   Edit `lib/public_suffix/version.rb` and update the `VERSION` constant:
-
-   ```ruby
-   VERSION = "X.Y.Z"
-   ```
-
-3. **Update the changelog** with the new version
-
-   Edit `CHANGELOG.md` and add a new section for the release following the [Common Changelog](https://common-changelog.org/) format (see [CONTRIBUTING.md](CONTRIBUTING.md) for details):
-
-   ```markdown
-   ## X.Y.Z - YYYY-MM-DD
-
-   ### Changed
-
-   - Description of changes
-   ```
-
-4. **Install dependencies**
-
-   ```shell
-   bundle install
-   ```
-
-   or simply:
-
-   ```shell
-   bundle
-   ```
-
-5. **Run tests** and confirm they pass
-
-   ```shell
-   bundle exec rake test
-   ```
-
-6. **Commit the new version**
-
-   ```shell
-   git commit -am "Release $VERSION"
-   ```
-
-7. **Create a signed tag**
-
-   ```shell
-   git tag -a v$VERSION -s -m "Release $VERSION"
-   ```
-
-8. **Push the changes and tag**
-
-   ```shell
-   git push origin main
-   git push origin v$VERSION
-   ```
-
-9. **Build and publish the gem**
-
-   ```shell
-   bundle exec rake release
-   ```
-
-   This will:
-   - Build the gem
-   - Push it to RubyGems
-   - Create a GitHub release
-
-## Post-release
-
-- Verify the new version appears on [RubyGems](https://rubygems.org/gems/public_suffix)
-- Verify the GitHub release was created
-- Announce the release if necessary