-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
🌱 Update Update Golang Dependencies group
| datasource | package | from | to | | ---------- | ------------------------- | ------- | ------- | | go | github.com/google/cel-go | v0.20.1 | v0.22.1 | | go | github.com/onsi/ginkgo/v2 | v2.19.1 | v2.22.0 | | go | github.com/onsi/gomega | v1.34.0 | v1.35.1 | | go | golang.org/x/mod | v0.18.0 | v0.22.0 | | go | golang.org/x/oauth2 | v0.21.0 | v0.24.0 | | go | sigs.k8s.io/kind | v0.23.0 | v0.25.0 |
- Loading branch information
1 parent
60e88ff
commit 83dfda6
Showing
286 changed files
with
15,965 additions
and
12,285 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1 +1 @@ | ||
| 1.1.22 | ||
| 1.1.23 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,2 @@ | ||
| 7.0.1 | ||
| # Keep this pinned version in parity with cel-go |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,2 @@ | ||
| *.pb.go linguist-generated=true | ||
| *.pb.go -diff -merge |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,2 @@ | ||
| bazel-* | ||
| MODULE.bazel.lock |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,34 @@ | ||
| load("@io_bazel_rules_go//go:def.bzl", "go_library") | ||
|
|
||
| package(default_visibility = ["//visibility:public"]) | ||
|
|
||
| licenses(["notice"]) # Apache 2.0 | ||
|
|
||
| go_library( | ||
| name = "expr", | ||
| srcs = [ | ||
| "checked.pb.go", | ||
| "eval.pb.go", | ||
| "explain.pb.go", | ||
| "syntax.pb.go", | ||
| "value.pb.go", | ||
| ], | ||
| importpath = "cel.dev/expr", | ||
| visibility = ["//visibility:public"], | ||
| deps = [ | ||
| "@org_golang_google_genproto_googleapis_rpc//status:go_default_library", | ||
| "@org_golang_google_protobuf//reflect/protoreflect", | ||
| "@org_golang_google_protobuf//runtime/protoimpl", | ||
| "@org_golang_google_protobuf//types/known/anypb", | ||
| "@org_golang_google_protobuf//types/known/durationpb", | ||
| "@org_golang_google_protobuf//types/known/emptypb", | ||
| "@org_golang_google_protobuf//types/known/structpb", | ||
| "@org_golang_google_protobuf//types/known/timestamppb", | ||
| ], | ||
| ) | ||
|
|
||
| alias( | ||
| name = "go_default_library", | ||
| actual = ":expr", | ||
| visibility = ["//visibility:public"], | ||
| ) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,25 @@ | ||
| # Contributor Code of Conduct | ||
| ## Version 0.1.1 (adapted from 0.3b-angular) | ||
|
|
||
| As contributors and maintainers of the Common Expression Language | ||
| (CEL) project, we pledge to respect everyone who contributes by | ||
| posting issues, updating documentation, submitting pull requests, | ||
| providing feedback in comments, and any other activities. | ||
|
|
||
| Communication through any of CEL's channels (GitHub, Gitter, IRC, | ||
| mailing lists, Google+, Twitter, etc.) must be constructive and never | ||
| resort to personal attacks, trolling, public or private harassment, | ||
| insults, or other unprofessional conduct. | ||
|
|
||
| We promise to extend courtesy and respect to everyone involved in this | ||
| project regardless of gender, gender identity, sexual orientation, | ||
| disability, age, race, ethnicity, religion, or level of experience. We | ||
| expect anyone contributing to the project to do the same. | ||
|
|
||
| If any member of the community violates this code of conduct, the | ||
| maintainers of the CEL project may take action, removing issues, | ||
| comments, and PRs or blocking accounts as deemed appropriate. | ||
|
|
||
| If you are subject to or witness unacceptable behavior, or have any | ||
| other concerns, please email us at | ||
| [[email protected]](mailto:[email protected]). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,32 @@ | ||
| # How to Contribute | ||
|
|
||
| We'd love to accept your patches and contributions to this project. There are a | ||
| few guidelines you need to follow. | ||
|
|
||
| ## Contributor License Agreement | ||
|
|
||
| Contributions to this project must be accompanied by a Contributor License | ||
| Agreement. You (or your employer) retain the copyright to your contribution, | ||
| this simply gives us permission to use and redistribute your contributions as | ||
| part of the project. Head over to <https://cla.developers.google.com/> to see | ||
| your current agreements on file or to sign a new one. | ||
|
|
||
| You generally only need to submit a CLA once, so if you've already submitted one | ||
| (even if it was for a different project), you probably don't need to do it | ||
| again. | ||
|
|
||
| ## Code reviews | ||
|
|
||
| All submissions, including submissions by project members, require review. We | ||
| use GitHub pull requests for this purpose. Consult | ||
| [GitHub Help](https://help.github.com/articles/about-pull-requests/) for more | ||
| information on using pull requests. | ||
|
|
||
| ## What to expect from maintainers | ||
|
|
||
| Expect maintainers to respond to new issues or pull requests within a week. | ||
| For outstanding and ongoing issues and particularly for long-running | ||
| pull requests, expect the maintainers to review within a week of a | ||
| contributor asking for a new review. There is no commitment to resolution -- | ||
| merging or closing a pull request, or fixing or closing an issue -- because some | ||
| issues will require more discussion than others. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,43 @@ | ||
| # Project Governance | ||
|
|
||
| This document defines the governance process for the CEL language. CEL is | ||
| Google-developed, but openly governed. Major contributors to the CEL | ||
| specification and its corresponding implementations constitute the CEL | ||
| Language Council. New members may be added by a unanimous vote of the | ||
| Council. | ||
|
|
||
| The MAINTAINERS.md file lists the members of the CEL Language Council, and | ||
| unofficially indicates the "areas of expertise" of each member with respect | ||
| to the publicly available CEL repos. | ||
|
|
||
| ## Code Changes | ||
|
|
||
| Code changes must follow the standard pull request (PR) model documented in the | ||
| CONTRIBUTING.md for each CEL repo. All fixes and features must be reviewed by a | ||
| maintainer. The maintainer reserves the right to request that any feature | ||
| request (FR) or PR be reviewed by the language council. | ||
|
|
||
| ## Syntax and Semantic Changes | ||
|
|
||
| Syntactic and semantic changes must be reviewed by the CEL Language Council. | ||
| Maintainers may also request language council review at their discretion. | ||
|
|
||
| The review process is as follows: | ||
|
|
||
| - Create a Feature Request in the CEL-Spec repo. The feature description will | ||
| serve as an abstract for the detailed design document. | ||
| - Co-develop a design document with the Language Council. | ||
| - Once the proposer gives the design document approval, the document will be | ||
| linked to the FR in the CEL-Spec repo and opened for comments to members of | ||
| the [email protected]. | ||
| - The Language Council will review the design doc at the next council meeting | ||
| (once every three weeks) and the council decision included in the document. | ||
|
|
||
| If the proposal is approved, the spec will be updated by a maintainer (if | ||
| applicable) and a rationale will be included in the CEL-Spec wiki to ensure | ||
| future developers may follow CEL's growth and direction over time. | ||
|
|
||
| Approved proposals may be implemented by the proposer or by the maintainers as | ||
| the parties see fit. At the discretion of the maintainer, changes from the | ||
| approved design are permitted during implementation if they improve the user | ||
| experience and clarity of the feature. |
Oops, something went wrong.