Skip to content

Pinning files: describe the monorepo, not the copier template - #55

Merged
Tobias-Fischer merged 1 commit into
mainfrom
pinning-comments
Oct 10, 2026
Merged

Tobias-Fischer merged 1 commit into
mainfrom
pinning-comments

Conversation

@Tobias-Fischer

Copy link
Copy Markdown
Collaborator

The headers of shared/pinning/conda_forge.yaml and shared/pinning/overrides.yaml still referred to the copier template (template/vinca_pinning.yaml.jinja, "copier answers").

They now describe how the files are used:

  • rs <d> render-pinning combines them into distros/<d>/conda_build_config.yaml;
  • conda_forge_pinning_version/conda_forge_migrations in a distribution's distro.yaml take precedence, with a pointer to RoboStack monorepo: remaining setup and maintainer feedback #54 (all distributions on the shared pinning);
  • a distribution's own pinning_overrides replace shared entries of the same name.

Comments only: the rendered pinning doesn't change, and rs check passes. Part of #54.

🤖 Generated with Claude Code

The headers of shared/pinning/conda_forge.yaml and overrides.yaml still
referred to the copier template (template/vinca_pinning.yaml.jinja, copier
answers). Comments only; the rendered pinning is unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Tobias-Fischer
Tobias-Fischer merged commit a421f43 into main Oct 10, 2026
14 of 22 checks passed
@Tobias-Fischer
Tobias-Fischer deleted the pinning-comments branch October 10, 2026 04:23
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