Skip to content

bump: .cfg.toml should not track template-bundles.yml as a bumpversion file in downstream repos #44

@HarryCampion

Description

@HarryCampion

Problem

.rhiza/.cfg.toml includes a [[tool.bumpversion.files]] entry for .rhiza/template-bundles.yml:

[[tool.bumpversion.files]]
filename = ".rhiza/template-bundles.yml"
version_template = "version: {current_version}"
search = "version: {current_version}"
replace = "version: {new_version}"
regex = false
ignore_missing_files = true

template-bundles.yml is a rhiza-go template artefact — it belongs to the template repo itself, not to downstream projects. When a downstream repo syncs .rhiza/.cfg.toml, make bump attempts to rewrite the version string in that file. If the downstream excludes template-bundles.yml from sync (as expected), the bump either silently no-ops (because ignore_missing_files = true) or produces confusing behaviour.

A downstream project had to patch this out manually by removing the stanza from .cfg.toml and excluding the file in template.yml.

Suggestion

Remove the template-bundles.yml bumpversion entry from .cfg.toml in the template. Version tracking for template-bundles.yml should be handled within the template repo itself (e.g. via a separate, template-only bumpversion config or a dedicated make target), not baked into the config that is synced downstream.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions