Prebuild Publishing Targets to Miinimize Chances of Releases Breaking

[KetanReddy]

Change Type (required)

Indicate the type of change your pull request is:

• patch
• minor
• major
• N/A

Does your PR have any documentation updates?

• Updated docs
• No Update needed
• Unable to update docs

📦 Published PR as canary version: 0.11.1--canary.650.22896

Try this version out locally by upgrading relevant packages to 0.11.1--canary.650.22896

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.38%. Comparing base (40e8a6e) to head (9c1e9a7).
Report is 32 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #650      +/-   ##
==========================================
- Coverage   90.39%   90.38%   -0.01%     
==========================================
  Files         333      333              
  Lines       20564    20564              
  Branches     1987     1987              
==========================================
- Hits        18588    18587       -1     
- Misses       1962     1963       +1     
  Partials       14       14              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[KetanReddy]

/canary

[sugarmanz]

Can merge this comment w/ the Maven Central Prepublish comment — they're the same thing.

[sugarmanz]

Should move the echos until where we actually publish

[sugarmanz]

Should build the explicit target that we're going to run, //docs:gh_deploy — not everything under docs, as it might not all be applicable for publishing docs.