Release version 0.6.0

[ginnyTheCat]

There have been quite a few changes since the 0.5.0 release that would probably be worth a 0.6.0 release.

• Update to mupdf v1.26.0-rc1 and fix leak #135
• Fix build on windows-2022 and windows-2025 (visual studio 2022) #139
• Refactor mupdf-sys build script #136
• Add initial OCR support in document_writer #141
• Add bounds check and get rid of allocation for set_{user,owner}_password #142
• Move to_{html,xhtml,xml,text,json} methods from Page to TextPage #143 (breaking change)
• Return more information for outlines #145 (breaking change)
• Shorten enum names in mupdf_sys #152 (breaking change)
• Extension of the Rect and IRect structs #156
• Fix mupdf build with clang 17 on macOS #133 and Fix mupdf build on macOS #161
• importantly Fix memory safety of native device #164 (breaking change)
• Implement to_svg for DisplayList #166
• Use macro to simplify common wrapper operations #168
• Add more functions to support annotation operations #169
• Add more annotation functions #171
• Extend from_enum macro to keep all enums at smallest repr #172
• importantly Handle samples being null if empty (w=0 and h=0) #176

One thing that might be worth doing before pushing this would be to implement one of the solutions from #149 (comment) as otherwise mupdf-sys generates a lot of warnings on windows with rustc below version 1.89.0 (the latest stable version).

Probably 0.5.0 should be yanked after, due to #142, #176 and #159 (technically even all versions except for 0.0.1 because of 054f619)

[messense]

I've configured trusted publishing in crates.io for both mupdf-sys and mupdf, feel free to setup a github action to automate the publish process.

[Trojanking123]

any update on this ?

[ginnyTheCat]

One thing that might be worth doing before pushing this would be to implement one of the solutions from #149 (comment) as otherwise mupdf-sys generates a lot of warnings on windows with rustc below version 1.89.0 (the latest stable version).

This is still unresolved but I will probably come back to that in the next few days.

[hollisticated-horse]

anyone have a good example of another project's github-actions for publishing ?

[vincent-uden]

I'd really love to see 0.6.0 pushed to release and I'm willing to help push it over the line if needed/wanted.

What's the proposed mechanism for the github action?

1. Create a release on github
2. Action runs on release to compile and publish to crates.io

What is supposed to happen if the publish fails? For example if someone has forgotten to bump the version number in Cargo.toml.
I'm sure there are other possible failure states as well.

I already have an action that compiles my Rust project on creating a release, that should be easily repurposed into a cargo publish action if there are no well established ones already.

[messense]

@vincent-uden here is the documentation which has a github actions example: https://crates.io/docs/trusted-publishing

[vincent-uden]

I kinda outlined all of in the PR but now it is done.

We could almost just use the example from crates.io, the only thing that needed to be added was installing libfontconfig1-dev before compiling.

I think it should match your configuration @messense as long as you have setup the publish environment already

[messense]

as long as you have setup the publish environment already

it was set up.

[ginnyTheCat]

Are there any things somebody would like to do before the release, or is everything ready?

[pratyushmittal]

Not sure if this is a bug, but the latest release 0.6.0 doesn't show on docs.rs.

• 0.6.0 Release: https://github.com/messense/mupdf-rs/releases
• Doc.rs: https://docs.rs/mupdf/latest/mupdf/

Running cargo update still catches only 0.5.0.

[ginnyTheCat]

Yea, the publish GitHub action had some bugs. Maybe the 4th try now is gonna work 🤪

[ginnyTheCat]

Well, didn't work either. The mupdf-sys tar is too big to be published on crates.io. This needs to be fixed before this release can happen.

the remote server responded with an error (status 413 Payload Too Large): max upload size is: 15728640

This is the same problem as #72.