📣 Masa Bittensor release v1.4

[mudler]

🗺 What's left for release

<List of items with remaining PRs and/or Issues to be considered for this release>

🐛 Bug fixes

• item_1

🌍 Bittensor

• Feat: Deploy single miner with protocol cluster behind it masa-bittensor#238
• Spike: Create WebSockets, so we can integrate our Twitter scraper with enabled push functionality masa-bittensor#241
• Spike: Investigate and Model Fair Distribution of Validator Requests to Miners masa-bittensor#258
• [EPIC]: TEE #87

🧪 Code testing

• item_1

🚑 Code health

• item_1

🔍 Services

• item_1

📡 Testnet Environment

• item_1

🤖 CI and release process

• item_1

🎁 Product:

• item_1

💻 Infra

• item_1

🔮 Metrics

• item_1

📖 Documentation

• item_1

🔦 Highlights

< top highlights for this release notes >

Release Checklist

Security

• Ensure dependencies are up to date and there are no known vulnerabilities. Run pip list --outdated to see outdated dependencies. If any dependencies need upgrading (and are in fact upgraded), run pip freeze > requirements.txt to update the requirements!

Continuous Integration (CI)

• Ensure all CI tests are passing
  • Docker Build and Publish / check-and-build (subtensor)
  • Docker Build and Publish / check-and-build (subnet)
  • Docker Build and Publish / check-and-build (miner)
  • Docker Build and Publish / check-and-build (validator)
  • Docker Build and Publish / check-and-build (protocol)
    it is possible that we will de-couple the protocol CI build and check in future iterations

Issue Tracking

• Verify there are no blockers to the release
  a typical release will look like this, verify all issues are resolved!

Tagging

• Tag the masa-bittensor release, and ensure the latest tag is visible here

Release Notes

• Update release notes text. An example of a previous release is here, built off of the release.yml configuration here
• Ensure the latest release notes are captured here so they automatically get published to our dev docs.

Docker

• Confirm that Docker images are published correctly
  this was resolved in #160 and should work automatically!

Documentation

• Ensure documentation is updated. This includes our setup documentation as well as advanced sections. All markdown files here are automatically pushed to our developer docs website. If certain documents do not appear, edit the sidebar here
• Review and update installation instructions if needed: Installation Guide

Notifications

• Notify @giovaroma and @lacyg4.
• Ask DCG to bump the weights_version - btcli sudo set --param weights_version --value --netuid 42