Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • beat.core beat.core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 14
    • Issues 14
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • beatbeat
  • beat.corebeat.core
  • Issues
  • #80
Closed
Open
Issue created May 06, 2019 by Jaden DIEFENBAUGH@jdiefenbaughContributor

`jsonschema` & `beat-devel` version conflicts

I might have figured out the CI issues...specifying the new jsonschema version requirement in conda/meta.yaml conflicts with beat-devel:

UnsatisfiableError: The following specifications were found to be in conflict:
  - beat-devel=2019.04.30 -> jsonschema==2.6.0=py36h006f8b5_0
  - jsonschema[version='>=3.0.0']

Do we need to restrict jsonschema to 2.6.0 in beat-devel, or can we bump it to 3.x?

Assignee
Assign to
Time tracking