chore(release): 1.0.13-unstable.20260825222757

[github-actions]

Version bump for 1.0.13-unstable.20260825222757, opened by the release workflow.

The tag v1.0.13-unstable.20260825222757 already names this commit, so the released
package and its label agree. Merging this brings development up
to the released version.

Raised as a pull request rather than pushed directly because
development requires one; a direct push is rejected with GH013
and takes the release down with it.

[rubenvdlinde]

Closing as obsolete: development has advanced to 1.0.13-unstable.20260825094451, past this PR's 1.0.13-unstable.20260825222757, so the bump would move the version backwards. The release workflow regenerates a current one on its next run; the pile-up is fixed in ConductionNL/.github#578.

[rubenvdlinde]

Correction to my previous comment: this PR is not a backwards bump. It proposes a version newer than development's, so the earlier reason I gave was wrong. The PR is genuinely conflicting; checking which file actually conflicts.

[rubenvdlinde]

Correction. My closing comment gave the wrong reason. This PR proposed 1.0.13-unstable.20260825222757, which is newer than development's 1.0.13-unstable.20260825094451 — it was not a backwards bump.

The real reason it could not merge is that it conflicted on appinfo/info.xml: another release landed on development after this branch was cut, and both edit the same <version> line.

Closing was still the right outcome — the release workflow regenerates a current bump on its next run — but the stated reason was inaccurate, and the branch was deleted on close so this PR cannot be reopened. Recording it here so the history is not misleading. The pile-up that produced these is fixed in ConductionNL/.github#578.