Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
api
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
cubicweb
cubes
api
Commits
3e43614fdfee
Commit
3e43614fdfee
authored
2 years ago
by
Fabien Amarger
Browse files
Options
Downloads
Patches
Plain Diff
chore(pkginfo): Add a comment to explain why we need this dependency and how to resolve the issue
parent
211127a32ffc
Branches
branch/default
Branches containing commit
No related tags found
1 merge request
!27
fix(deps): read_yaml_file() is in openapi-spec-validator version 0.4 but not 0.5
Pipeline
#149443
passed
2 years ago
Stage: lint
Stage: tests
Changes
1
Pipelines
2
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
cubicweb_api/__pkginfo__.py
+3
-0
3 additions, 0 deletions
cubicweb_api/__pkginfo__.py
with
3 additions
and
0 deletions
cubicweb_api/__pkginfo__.py
+
3
−
0
View file @
3e43614f
...
...
@@ -34,6 +34,9 @@
"
cubicweb
"
:
"
>= 3.36.0
"
,
"
PyJWT
"
:
"
>= 2.4.0
"
,
"
pyramid-openapi3
"
:
"
>= 0.14
"
,
# force openapi-spec-validator to be in 0.4.x since the 0.5 breaks the API
# and "pyramid-openapi3" is not (yet) compatible
# TODO: update pyramid-openapi3 to be compatible with openapi-spec-validator@v0.5.x
"
openapi-spec-validator
"
:
"
>= 0.4, < 0.5
"
,
}
__recommends__
=
{}
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment