package.json declares version 3.13.0-opencode.1 (npm semver pre-release format: this version sorts before 3.13.0).
pyproject.toml declares version 3.13.0.post1 (PEP 440 post-release format: this version sorts after 3.13.0).
Both are meant to say "the OpenCode port of upstream v3.13.0," but one claims to be a pre-release and the other a post-release. This sends mixed signals and will cause confusion if either version is ever compared to upstream 3.13.0 in a registry or changelog tool.
Suggested fix: Pick one convention. If the port is "3.13.0 plus port-specific changes," then:
- pyproject.toml:
3.13.0.post1 (correct as-is, post-release in PEP 440)
- package.json:
3.13.0-opencode.1 → 3.13.1-opencode.0 or just 3.13.0 with a "port" metadata field
Alternatively, document in MIGRATION.md why the two differ and that it is intentional.
package.jsondeclares version3.13.0-opencode.1(npm semver pre-release format: this version sorts before 3.13.0).pyproject.tomldeclares version3.13.0.post1(PEP 440 post-release format: this version sorts after 3.13.0).Both are meant to say "the OpenCode port of upstream v3.13.0," but one claims to be a pre-release and the other a post-release. This sends mixed signals and will cause confusion if either version is ever compared to upstream 3.13.0 in a registry or changelog tool.
Suggested fix: Pick one convention. If the port is "3.13.0 plus port-specific changes," then:
3.13.0.post1(correct as-is, post-release in PEP 440)3.13.0-opencode.1→3.13.1-opencode.0or just3.13.0with a"port"metadata fieldAlternatively, document in MIGRATION.md why the two differ and that it is intentional.