Thanks for your interest to this docker image !
If you're facing a bug when compiling a document, please do the following before submitting an issue:
-
Fetch the latest version with
docker pull dalibo/pandocker:latest
and check if the error remains. -
Read the SYNTAX specs and check that you used the correct markdown syntax
- Run
make all
locally to build your modifications before submitting - Run
make test
to pass all the regession tests - Check that you have included the media files necessary to test your patch
- Check for the latest release of Pandoc here: https://github.com/jgm/pandoc/releases
- Check for the latest release of Crossref here: https://github.com/lierdakil/pandoc-crossref/releases
- Modify the
PANDOC_VERSION
andPANDOC_CROSSREF_VERSION
variables in the Makefile - Modify the
PANDOC_VERSION
andPANDOC_CROSSREF_VERSION
variables in the buster/Dockerfile - Modify the image tag and
PANDOC_CROSSREF_VERSION
variable in the alpine/Dockerfile
If you submit a patch to this project, the name and the email address you give us may be embedded in the public repository. The removal of this information would break the code history and would be impermissibly destructive to the project and the interests of all those who contribute or benefit from it.
As an open source project, we consider that we must maintain this information in the repository for archiving purposes in the public interest.
Let's say you want to release version 23.07
- Close all open ticket on the current milestone
- Create a
release
branch - Update the CHANGELOG.md
- Add
23.07
inon.push.branches
in .github/workflows/docker_hub.yml - Write a announcement in NEWS.md
- Merge the
release
branch intolatest
- Add a tag
23.07
tolatest
- Create a new release
- Rebase the
stable
branch fromlatest
- Create a
23.07
branch fromlatest
- Check that github Actions is correctly publishing the images
- Create the next milestone
- Bump the new version on
latest
- Publish the announcement
- Bump to the new version in CHANGELOG.md
- Close the current milestone