Skip to content

Add FAQ entry explaining pkg.go.dev module paths #1432

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
TristonianJones merged 1 commit into from
Aug 21, 2026
Merged

Add FAQ entry explaining pkg.go.dev module paths #1432

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -266,6 +266,14 @@ runtime bindings and error handling to do the right thing.
* See the [CEL C++][3] toolchain (under development) for information about how
to integrate CEL evaluation into other environments.

### Why are there multiple entries for cel-go on pkg.go.dev?

Due to historical changes in the module path defined in `go.mod`, documentation on `pkg.go.dev` is split across different paths depending on the version range:

* **[cel.dev/cel-go](https://pkg.go.dev/cel.dev/cel-go)**: Canonical path for **v0.32.0** and newer.
* **[github.com/google/cel-go](https://pkg.go.dev/github.com/google/cel-go)**: Path for versions **v0.2.0** through **v0.31.0**.
* **[github.com/cel-expr/cel-go](https://pkg.go.dev/github.com/cel-expr/cel-go)**: Only contains **v0.1.0** (tagged before `go.mod` was introduced).

### How can I contribute?

* See [CONTRIBUTING.md](./CONTRIBUTING.md) to get started.
Expand Down
Loading