[DON'T MERGE] chore: bump @formspree/deploy to ^0.3.4 so --force reaches the API

[vitormorales]

Changes proposed in this pull request:

• Bump @formspree/deploy from ^0.3.3 to ^0.3.4 in package.json and refresh package-lock.json.
• Lockfile also drops the nested axios@0.21.1 / follow-redirects@1.13.1 that 0.3.3 carried — 0.3.4 now dedupes to the top-level axios.

Public description:

• Internal Improvement (no customer impact)
• Hide from Changelog

Have you made sure to add:

• Tests
• Documentation

Supplemental Screenshots and GIFs

[Insert screenshot or GIFs of old and new behavior to assist reviewers]

Steps to Review

See https://www.notion.so/formspree/Code-Reviews-78c7d523c4424f66a399367a6738ae13

Any Additional Information or Deployment Notes

DON'T MERGE UNTIL formspree/formspree-deploy#9 IS OUT

[greptile-apps]

Greptile Summary

The PR upgrades @formspree/deploy from 0.3.3 to 0.3.4 so the existing --force argument reaches the deployment API.

• Updates the dependency range and locked package artifact.
• Deduplicates the deploy package’s nested axios and follow-redirects copies to the identical top-level versions.

Confidence Score: 5/5

The PR appears safe to merge, with no concrete changed-code failure identified.

The upgraded package retains the CLI’s supported Node requirement, and the lockfile deduplication preserves the exact axios and follow-redirects versions previously used by the deploy package.

Important Files Changed

Filename	Overview
package.json	Updates @formspree/deploy’s minimum compatible version from 0.3.3 to 0.3.4 without changing other dependency declarations.
package-lock.json	Locks @formspree/deploy 0.3.4 and safely deduplicates its transitive dependencies to identical top-level versions.

_{Reviews (1): Last reviewed commit: "chore: update deploy package release" | Re-trigger Greptile}