ci: also move minor version tag on release

[Swimburger]

Summary

Extends the release workflow to also force-update the minor version tag when a semver release is published. Previously, publishing v1.1.0 would only update the v1 tag. Now it also updates v1.1, so consumers pinned to @v1.1 get patch updates automatically.

The minor tag is only created when the release tag has 3+ version parts (e.g., v1.1.0 → updates v1 + v1.1). Two-part tags like v1.1 only update the major tag v1.

This is the same change already shipped and verified in fern-api/sync-openapi, where it ran successfully for the v4.0.0 release.

Review & Testing Checklist for Human

• Verify tag parsing handles your release tag format. The script expects vX.Y.Z tags. If this repo uses a different convention (e.g., setup-fern-cli@1.0.0), the sed 's/^v//' strip would not work correctly.
• Test with a patch release (e.g., publish v1.0.1) and confirm both v1 and v1.0 tags are updated. The sync-openapi repo already validated v4.0.0 → v4 + v4.0, but this repo hasn't been tested yet.

Notes

• Link to Devin Session
• Requested by: @Swimburger

---

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 3 additional findings.