📣 Masa Protocol release v0.7

[mudler]

🗺 What's left for release

Missing: masa-finance/masa-oracle#537

• fix(ci): point correctly to main in goreleaser.yml by @mudler in fix(ci): point correctly to main in goreleaser.yml masa-oracle#516
• hotfix: swagger bug fixes by @teslashibe in hotfix: swagger bug fixes masa-oracle#511
• feat(tests): add baseline for an integration test by @mudler in feat(tests): add baseline for an integration test masa-oracle#527
• fix: multiaddress not constructed on startup by @teslashibe in fix: multiaddress not constructed on startup masa-oracle#524
• chore: revert back changes to fix integration tests by @mudler in chore: revert back changes to fix integration tests masa-oracle#529

🌍 Protocol/P2P

• SPIKE: Worker selection heuristics #12
• Add Initial Analytics Event Triggers masa-oracle#419
• spike: refactor nodeData updates to optimize gossip and allow only a validator to distribute nodeData #66

Scraper

• chore: add 2fa support for Telegram masa-oracle#490

🧪 Code testing

• QA issues that are fixed in v0.6 masa-oracle#448

🎁 Product:

• spike: research developer playground for Protocol API #31
• spike: static data sets: Twitter, Discord, Web, Podcast (Diarization) #38
• https://github.com/masa-finance/product-issues/issues/7

💻 Infra

• Users are able to easily access Swagger with no need to setup an environment masa-oracle#451
• Separate protocol version and application version masa-oracle#499

CI

• ci: goreleaser pipeline fails masa-oracle#514

🔦 Highlights

This release will feature hardening on the worker selection strategies.

✅ Release Checklist

• Stage 0 - Finishing Touches
  • Make sure CI tests are passing.
  • chore: bump protocol version to v0.7.0 masa-oracle#537 is merged
  • Ensure SDK is aligned to have the neded Oracle features exposed for the release
  • Ensure the CLI is aligned to consume the latest SDK correctly
  • There is a Masa-Oracle release
  • Update release files to bump the version in the Oracle
• Stage 1 - Manual testing
  • How: Using the assets from master, make sure that test scenarios not covered by automatic tests are passing, and that docs are still aligned
    • ...
• Stage 3 - Release
  • Tag Oracle
  • Tag SDK
  • CLI and App needs to point to SDK version and have its own tag
• Stage 4 - After release
  • Release notes needs to be updated in the documentation here: https://developers.masa.ai/docs/masa-oracle/RELEASE_NOTES
  • Update notion documentation about release