Allow Specifying Package Version for ZIP Archive Packages to Support Development Branches

[yusancky]

Background

Currently, when managing ZIP archive packages, the SemVer version is always read from the package's typst.toml (or gets 0.0.0). This design requires users who need to use a development branch to frequently modify their Typst files just to update the version reference, which is a boring and inconvenient job for users working with actively developed packages.

It would be more user-friendly if the action allowed specifying a package version manually when needed, rather than always relying on the version declared in typst.toml. This would help users who want to use a specific branch or development snapshot without having to constantly update their Typst files.

Suggestion

• Add an option to override the package version read from typst.toml by explicitly specifying the desired version in the workflow or configuration.
• Other solutions?