Skip to content
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.

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

Update request: pandoc 3.1.11.1 → 3.5 #348028

Open
1 task done
amacfie opened this issue Oct 12, 2024 · 3 comments
Open
1 task done

Update request: pandoc 3.1.11.1 → 3.5 #348028

amacfie opened this issue Oct 12, 2024 · 3 comments
Labels
9.needs: package (update) This needs a package to be updated

Comments

@amacfie
Copy link

amacfie commented Oct 12, 2024

  • Package name: pandoc
  • Latest released version: 3.5
  • Current version on the unstable channel: 3.1.11.1
  • Current version on the stable/release channel: 3.1.11.1

Notify maintainers

@maralorn


Note for maintainers: Please tag this issue in your PR.


Add a 👍 reaction to issues you find important.

@amacfie amacfie added the 9.needs: package (update) This needs a package to be updated label Oct 12, 2024
@maralorn
Copy link
Member

Just as an explanation: The current mode of operations for packages contained in stackage is that we follow the package version in Stackage LTS. This saves us a lot of manual maintenance effort, but it means that we do not have the newest packages.

An update of stackage LTS is expected within the next 6 months.

@tjni tjni mentioned this issue Nov 14, 2024
13 tasks
@Atemu
Copy link
Member

Atemu commented Nov 23, 2024

Would it be possible to make an exception here?

You wouldn't want to do such manual work for the bulk of the haskellPackages, I'm fully with you there, but pandoc aint no obscure library that people use indirectly at best; it's an extremely widely-used CLI tool.

I'm sure there's only a handful of packages where this applies (shellcheck and git-annex come to mind) but that's a rather bounded set, so there isn't a great risk of exploding maintenance overhead.

@maralorn
Copy link
Member

Yeah, sure. Actually that work is already being done in #357687

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
9.needs: package (update) This needs a package to be updated
Projects
None yet
Development

No branches or pull requests

3 participants