[cristipufu]

Summary

• Fixes the crates.io publish. The 1.3.0 crate didn't publish (run). cargo publish builds the crate before uploading it, and the release job doesn't install the GTK/WebKit libraries that ci.yml installs, so glib-sys failed to build. The job now installs the same packages first. The token was fine.
• Makes publishing a release safe to retry. Each job checks its registry and skips a version that's already there. Publishing the release again then retries only what failed. For 1.3.0 that means the crate gets published and npm skips 0.7.0, which already went out.

Retrying 1.3.0 after merging

The release workflow runs the workflow file from the tag's commit, so the 1.3.0 tag has to move to this PR's merge commit:

1. Set the release back to draft.
2. Move the tag to the merge commit. The plugin's code is unchanged; only release.yml differs.
3. Publish the release again.

Test plan

• The "already published?" checks, run locally against the live registries:
  • crates.io: 1.0.0 skips, 1.3.0 publishes
  • npm: 0.7.0 skips, 0.8.0 publishes
• cargo publish --dry-run passes for 1.3.0 locally (on macOS, which already has the system libraries)
• Retry 1.3.0: the crates job publishes and the npm job skips 0.7.0

🤖 Generated with Claude Code