feat(TU-34343): Create new AWS Deploy workflow

[tom-ridsdale]

Summary

• Decouple AWS deployment from semantic-release by creating a separate workflow triggered by GitHub release events
• Simplify the release flow which is currently confusing and difficult to debug

Why

The current release flow is convoluted and hard to follow, focusing on embed since embed-react is NOT deployed to AWS:

  release.yml
    └─ yarn add -W @typeform/jarvis
    └─ git checkout HEAD -- package.json  # revert so jarvis isn't committed
    └─ yarn release
         └─ scripts/release.sh
              └─ yarn release-vanilla (embed)
                   └─ semantic-release
                        └─ @semantic-release/npm prepare  # ⚠️ suspect this removes jarvis from node_modules but not totally sure, it's difficult to debug!
                        └─ @semantic-release/npm publish
                        └─ @semantic-release/exec successCmd
                             └─ yarn post-release
                                  └─ yarn release:github  # npm publish to GitHub Packages
                                  └─ yarn release:aws
                                       └─ yarn release:aws:prepare
                                            └─ sh ./scripts/prepare-release.sh  # copies build files
                                       └─ yarn release:aws:deploy
                                            └─ jarvis deploy  # ❌ FAILS - jarvis not available!

New approach:

  release.yml (on push to main)
    └─ yarn release
         └─ scripts/release.sh
              └─ yarn release-vanilla (embed)
                   └─ semantic-release
                        └─ @semantic-release/npm prepare
                        └─ @semantic-release/npm publish
                        └─ @semantic-release/exec successCmd
                             └─ yarn post-release
                                  └─ yarn release:github  # npm publish to GitHub Packages
                        └─ @semantic-release/github  # creates GitHub release ─────┐
                                                                                   │
  deploy-aws.yml (triggered by GitHub release event) <─────────────────────────────┘
    └─ yarn add -W @typeform/jarvis # install jarvis
    └─ git checkout HEAD -- package.json  # revert so jarvis isn't committed
    └─ yarn release:aws
         └─ yarn release:aws:prepare
              └─ sh ./scripts/prepare-release.sh  # copies build files
         └─ yarn release:aws:deploy
              └─ jarvis deploy  # ✅ hopefully works - jarvis is installed!

This still only deploys to AWS when there are actual changes - since the AWS workflow only triggers when a GitHub release is created, and releases only happen when semantic-release detects releasable commits.

I am expecting that it will trigger when embed OR embed-react GitHub releases are published, but the IF condition on the workflow should mean it runs for the former and is skipped for the latter.

[typeform-ops-gha]

[BOT] Preview available with hash 291822d6de8380441aeb05db01150e33ca183821 here.

[sonarqubecloud]

Quality Gate passed

Issues
60 New issues
0 Accepted issues

Measures
1 Security Hotspot
76.5% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[gitstream-cm]

🥷 Code experts: tf-security

tf-security has most 👩‍💻 activity in the files.
tf-security has most 🧠 knowledge in the files.

See details

.github/workflows/release.yml

Activity based on git-commit:

	tf-security
DEC
NOV
OCT
SEP
AUG
JUL	81 additions & 0 deletions

Knowledge based on git-blame:
tf-security: 81%

packages/embed/package.json

Activity based on git-commit:

	tf-security
DEC
NOV
OCT
SEP
AUG
JUL	77 additions & 0 deletions

Knowledge based on git-blame:
tf-security: 93%

✨ Comment /gs review for LinearB AI review. Learn how to automate it here.

[typeform-ops-gha]

🎉 This PR is included in version @typeform/embed-v5.9.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀