Skip to content

Comments

feat: Release v2.0 with paging-go module rename#13

Merged
josemarluedke merged 2 commits intomainfrom
feat/v2-rename-to-paging-go
Dec 14, 2025
Merged

feat: Release v2.0 with paging-go module rename#13
josemarluedke merged 2 commits intomainfrom
feat/v2-rename-to-paging-go

Conversation

@josemarluedke
Copy link
Member

Summary

This PR implements v2.0 of the pagination library with a breaking change to align with organizational naming standards.

Breaking Changes

1. Module Path Rename

  • Old: github.com/nrfta/go-paging
  • New: github.com/nrfta/paging-go/v2

This aligns with organizational naming conventions ({purpose}-go instead of go-{purpose}).

2. Import Updates

All imports throughout the codebase have been updated:

// Before
import "github.com/nrfta/go-paging"
import "github.com/nrfta/go-paging/offset"

// After
import "github.com/nrfta/paging-go/v2"
import "github.com/nrfta/paging-go/v2/offset"

Changes

Code (24 files)

  • Updated go.mod module declaration
  • Updated all package imports across:
    • Core package files
    • cursor/ package (6 files)
    • offset/ package (3 files)
    • quotafill/ package (3 files)
    • sqlboiler/ package (5 files)
    • tests/ package (4 files)

Documentation (2 files)

  • README.md: Updated title, badge, install command, and all code examples
  • MIGRATION.md: Comprehensive v0.3.0 → v2.0 migration guide with:
    • Breaking changes summary table
    • Step-by-step migration instructions
    • Updated code examples

Migration Path for Users

Users migrating from v0.3.0 have two changes to make:

  1. Update imports:

    # In go.mod
    require github.com/nrfta/paging-go/v2 v2.0.0
  2. Update import statements:

    import "github.com/nrfta/paging-go/v2/offset"

The MIGRATION.md file provides complete migration instructions.

Compatibility

  • v0.3.0 users: GitHub redirects ensure old import path continues working temporarily
  • All tests passing: 174/174 specs pass with new import paths
  • No API changes: Only the module path changed, all APIs remain identical

Release Plan

After merge:

  1. Tag v2.0.0
  2. Create GitHub release with migration guide
  3. Update any dependent services

🤖 Generated with Claude Code

josemarluedke and others added 2 commits December 13, 2025 17:21
Update all import paths across the codebase to use the new module path
github.com/nrfta/paging-go/v2, aligning with organizational naming standards
where tool names follow the pattern {name}-{language}.

Changes:
- Update go.mod module declaration
- Replace all imports: github.com/nrfta/go-paging → github.com/nrfta/paging-go/v2
- Update imports across 23 Go files (core, cursor, offset, quotafill, sqlboiler, tests)
- No functional changes to the codebase

BREAKING CHANGE: Module path has changed from github.com/nrfta/go-paging to
github.com/nrfta/paging-go/v2. All consumers must update their imports and
run `go get -u github.com/nrfta/paging-go/v2` to upgrade to v2.0.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Update all documentation to reflect the new module path and v2.0 release:

README.md:
- Update repository title: go-paging → paging-go
- Update badge URL to match new repository name
- Update install command: go get github.com/nrfta/paging-go/v2
- Replace all import examples throughout usage sections
- Update gqlgen.yml configuration examples

MIGRATION.md:
- Rename guide: "v0.3.0 to v1.0" → "v0.3.0 to v2.0"
- Add breaking changes summary table showing module path migration
- Update all code examples with new import paths
- Document combined changes: modular architecture + repository rename
- Clarify that v2.0 includes both architectural improvements and naming alignment

BREAKING CHANGE: All documentation now references github.com/nrfta/paging-go/v2.
Users upgrading from v0.3.0 must update both their imports and module references
to the new v2.0 module path.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@josemarluedke josemarluedke merged commit 5fa0628 into main Dec 14, 2025
1 of 2 checks passed
@josemarluedke josemarluedke deleted the feat/v2-rename-to-paging-go branch December 14, 2025 01:25
@josemarluedke josemarluedke added the Type: Breaking Change This is a Breaking Change label Dec 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Type: Breaking Change This is a Breaking Change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant