Skip to content

chore: release v0.7.1#229

Closed
amcheste-ai-agent[bot] wants to merge 1 commit into
developfrom
chore/release-v0.7.1
Closed

chore: release v0.7.1#229
amcheste-ai-agent[bot] wants to merge 1 commit into
developfrom
chore/release-v0.7.1

Conversation

@amcheste-ai-agent
Copy link
Copy Markdown
Contributor

Summary

Bumps VERSION and charts/claude-teams-operator/Chart.yaml to 0.7.1, cutting the "Documentation Site" milestone release.

Why 0.7.1 (and not 0.7.0)

A draft v0.7.0 release exists in GitHub but was never tagged or published. Skipping straight to v0.7.1 keeps the published-release sequence clean and lets that draft be deleted afterward.

What's in this release

Next steps after this PR merges

  1. Promote developmain via CLI --no-ff merge (per the release-flow rule in ~/.claude/CLAUDE.md)
  2. Tag main with v0.7.1 to trigger the release pipeline
  3. Delete the dangling v0.7.0 draft release on GitHub

Test plan

  • Local build verified — only VERSION + Chart.yaml touched
  • CI green on this PR (Lint, Tests, Build)
  • After merge, develop → main promotion + tag + pipeline complete cleanly

🤖 Generated with Claude Code

Bumps VERSION and Helm chart to 0.7.1, cutting the "Documentation Site"
milestone release. Skips a draft v0.7.0 that was never published.

v0.7.1 delivers:

  - kagents project brand introduction across README, badges, and
    KUBECON.md, plus the new mascot/banner imagery (#172, #199, #220,
    #224).

  - A full mkdocs-material documentation site under docs/ with CI
    deploy workflow (#194): Diátaxis nav, polished homepage, and a
    Getting Started tutorial (#195); three concept pages covering
    resources, coordination, and operations (#196); how-to guides for
    cloud installs (AKS, EKS, GKE) and operational recipes — budget
    alerts, dashboard exposure, shared storage (#197); and an
    auto-generated API reference produced from kubebuilder markers via
    crd-ref-docs, with a `make docs-api` target that always reinstalls
    the pinned version (#198).

  - Community baseline (#201): Code of Conduct, polished CONTRIBUTING,
    hardened SECURITY policy, expanded issue templates.

  - KubeCon NA 2026 CFP draft (#168) and submission tracking — the
    talk has now been submitted ahead of the May 31 deadline.

  - Dependency bumps: sigs.k8s.io/controller-runtime 0.23.3 → 0.24.0
    (#215, which transitively raises k8s.io/api, apimachinery,
    client-go to 0.36.0 and the go directive to 1.26.0),
    github.com/onsi/ginkgo/v2 2.28.2 → 2.28.3 (#216),
    actions/setup-python 5 → 6 (#219), release-drafter 6.4.0 → 7.3.0
    (#218).

  - Toolchain alignment for the Go 1.26 vet rules:
    fix(controller): the create-pr error path now passes the error as
    a printf argument instead of as the format string itself (#226),
    which also defends against `%` characters in error messages
    producing garbled Kubernetes events.

  - CI cleanup: remove the auto-assign-PR-creator workflow (#227)
    which conflicted with the documented assignee policy and failed
    outright on bot-authored PRs, and drop the Linear Issue Reference
    gate from validate.yml (#225).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: amcheste <13696614+amcheste@users.noreply.github.com>
@amcheste-ai-agent amcheste-ai-agent Bot requested a review from amcheste as a code owner May 11, 2026 22:23
@amcheste-ai-agent
Copy link
Copy Markdown
Contributor Author

Closing in favor of cutting v0.7.0 — the draft v0.7.0 release on GitHub was never published, so the next published version is v0.7.0, not v0.7.1. Replacement PR coming next.

@amcheste amcheste deleted the chore/release-v0.7.1 branch May 11, 2026 22:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant