Skip to content

fix(helm): use version_variables for Chart.yaml version bumping#33

Merged
charlie83Gs merged 1 commit intomainfrom
fix/semantic-release-chart-version
Mar 25, 2026
Merged

fix(helm): use version_variables for Chart.yaml version bumping#33
charlie83Gs merged 1 commit intomainfrom
fix/semantic-release-chart-version

Conversation

@charlie83Gs
Copy link
Copy Markdown
Contributor

Summary

The version_pattern config key doesn't exist in python-semantic-release. Chart.yaml has been stuck at 0.2.6 while pyproject.toml advanced to 0.2.10.

Fix: use version_variables (the correct config key for non-TOML files) and sync Chart.yaml to current version 0.2.10.

Ref: python-semantic-release docs

Test plan

  • Next release bumps both pyproject.toml and Chart.yaml
  • Flux picks up new chart version and triggers pod rollout

🤖 Generated with Claude Code

….yaml

python-semantic-release does not support version_pattern. The correct
config key for non-TOML files is version_variables with format
"file:variable". Also sync Chart.yaml to current version 0.2.10.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@charlie83Gs charlie83Gs merged commit 5f90c78 into main Mar 25, 2026
17 checks passed
@charlie83Gs charlie83Gs deleted the fix/semantic-release-chart-version branch March 25, 2026 15:29
charlie83Gs added a commit that referenced this pull request Mar 27, 2026
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
charlie83Gs added a commit that referenced this pull request Apr 20, 2026
…onPipeline (Phase 2 #32)

Adds ``kt_hatchet.composition.resolve_phase_settings(state, graph_id,
phase)`` — the shared helper that translates a running graph's
``GraphConfig`` into the ``phase_settings`` dict
``DecompositionPipeline`` now accepts (#31 / #276). Fails fast on
resolver error: a graph opting into a narrower composition MUST NOT
silently widen to Settings defaults on a transient DB hiccup —
matches the tenancy-invariant posture of
``_resolve_composition_selectors`` in ``web_search``.

Wired into the two Hatchet tasks that construct
``DecompositionPipeline`` directly:

- ``decompose_chunk_task`` (worker-search.workflows.search)
- ``decompose_source_task`` (worker-search.workflows.decompose)

Worker-nodes call sites (``GatherFactsPipeline``, ``BuildingPipeline``,
``NodePipeline``) go through ``AgentContext`` which doesn't expose
``graph_id`` — threading there lands in the companion #33 PR once
``AgentContext`` grows the knob.

5 new unit tests on the helper cover: composition present, graph_id
None fallback, services None fallback, resolver-raises-propagates
(authorization guard), unknown-phase-empty-dict.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
charlie83Gs added a commit that referenced this pull request Apr 20, 2026
… path (Phase 2 #33) (#278)

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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