Version: 1.0.0
This is the canonical version managed in internal/config/version.go.
CryptoFunk follows Semantic Versioning 2.0.0:
- MAJOR version (1.x.x): Incompatible API changes
- MINOR version (x.1.x): New functionality in a backwards-compatible manner
- PATCH version (x.x.1): Backwards-compatible bug fixes
The canonical version is defined in internal/config/version.go:
package config
// Version is the canonical version of CryptoFunk
const Version = "1.0.0"
func GetVersion() string {
return Version
}All Go code should import and use the centralized version:
import "github.com/ajitpratap0/cryptofunk/internal/config"
// Use config.Version or config.GetVersion()
version := config.VersionThe version is used in:
-
MCP Servers: All MCP servers report the canonical version in their initialize response
cmd/mcp-servers/market-data/main.gocmd/mcp-servers/technical-indicators/main.gocmd/mcp-servers/risk-analyzer/main.gocmd/mcp-servers/order-executor/main.go
-
Agents: All agents read version from config
- Agent configurations inherit version from config defaults
-
API Server: Reports version in health endpoints
GET /healthreturns system versionGET /api/v1/versionreturns version details
-
CLI Tools: Taskfile version command
task versiondisplays current version
-
Docker Images: Tagged with semantic version
cryptofunk/orchestrator:1.0.0cryptofunk/api:1.0.0- Also tagged with
:latestfor convenience
-
Documentation: Version headers in major docs
- README.md
- ARCHITECTURE.md
- API.md
- DEPLOYMENT.md
To update the version across the entire system:
-
Update the canonical version in
internal/config/version.go:const Version = "1.1.0"
-
Update documentation headers (if major/minor version change):
- README.md
- ARCHITECTURE.md
- TASKS.md
- API.md
- DEPLOYMENT.md
- MCP_GUIDE.md
-
Rebuild all binaries:
task build
-
Rebuild Docker images (if deploying):
docker-compose -f deployments/docker-compose.yml build
-
Update Kubernetes manifests (if using K8s):
# Update image tags in deployments/k8s/base/*.yaml # Or use Kustomize to override image tags
-
Commit the change:
git add internal/config/version.go docs/ git commit -m "chore: Bump version to 1.1.0" git tag v1.1.0 git push origin main --tags
The CI/CD pipeline automatically:
- Extracts version from
internal/config/version.go - Tags Docker images with the version
- Creates GitHub releases on version tags (v*)
- Updates deployment manifests with new image tags
- Initial production release
- All 10 phases complete
- LLM-powered multi-agent trading system
- Full MCP integration
- Docker and Kubernetes deployment support
- CI/CD pipeline with automated testing
- Production-ready monitoring and observability
- Initial development version
- Used during Phase 1-9 implementation
- Not recommended for production use
- Semantic Versioning: https://semver.org/
- Go Module Versioning: https://go.dev/doc/modules/version-numbers
- Docker Image Tagging: https://docs.docker.com/engine/reference/commandline/tag/
- Git Tagging: https://git-scm.com/book/en/v2/Git-Basics-Tagging