-
Notifications
You must be signed in to change notification settings - Fork 78
Description
Hi
I noticed that there is a Chocolatey package available for pandoc-crossref, but it doesn’t seem to be updated regularly.
For example, version 0.3.4.1 exists on Chocolatey, but newer releases are not consistently published.
I also noticed that some teams rely on specific pandoc-crossref versions that were built against specific Pandoc versions (e.g. Pandoc 3.6.4).
In practice, this means teams cannot always upgrade freely and instead need a known-good pandoc-crossref + Pandoc combination for reproducibility and compatibility.
Because of this, having properly versioned and reproducible Chocolatey packages becomes even more important.
Proposed idea
- Automatically generate a Chocolatey package when a new release is published
- Ideally trigger this from the GitHub Actions pipeline
- Include clear metadata about:
- pandoc-crossref version
- compatible / targeted Pandoc version (where applicable)
- Publish the package to Chocolatey (or at least produce the .nupkg artifact)
Why this could be useful
- Allows Windows users and teams to pin exact pandoc-crossref + Pandoc-compatible versions
- Avoids adding non-Chocolatey dependencies
- Keeps Chocolatey packages in sync with official releases
- Improves reproducibility across CI pipelines and documentation builds
- Reduces manual maintenance effort over time
I would be happy to:
- Prototype a Chocolatey packaging script (based on the current 0.3.4.1 package)
- Investigate how Pandoc version compatibility could be reflected in the package metadata or release process
- Explore integration into the existing GitHub Actions workflow
- Open a PR if this approach is acceptable to you
Before starting, I wanted to check if this is something you’d be open to maintaining in the project.
Thanks for your time, and great work on pandoc-crossref!