ipynb-0.3

Open
#8,173 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
22/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Domain
build-system

Research direction

The issue is a Stackage upper-bound report: ipynb-0.3 breaks the pandoc-3.13 bound, which comes from #8172, and the reporter says pandoc-3.14 also needs a bump. Read #8172 and the ipynb-0.3 changelog linked in the issue, then find where the ipynb bound is declared in the repository's package-set or constraints files. Done means the bound is updated so that ipynb-0.3 is allowed for the affected pandoc versions. The body contains a typo, "iypnb", so confirm the intended package name first.

Written by the indexing model from the issue text.

Description

ipynb-0.3 (changelog) (John MacFarlane [email protected] @jgm) is out of bounds for:

  • pandoc-3.13 (>=0.2 && < 0.3). John MacFarlane [email protected] @jgm, Stackage upper bounds. Used by: library

The pandoc-3.13 bound is from #8172, but even pandoc-3.14 needs to be bumped. So, I'm adding an upper bound to iypnb

Dominant language
Dockerfile
Stars
550
Forks
831
Avg merge
18h 10m
Merged PRs (30d)
13

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from commercialhaskell/stackage

All issues in commercialhaskell/stackage

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.