Release 0.6.1 - #12
Merged
Merged
Conversation
One fix: pyvider's configuration was being read from the wrong table. Plating looked for `component_packages` and the provider name in the top-level `[pyvider]` table. Both shipped provider repositories put them in `[tool.pyvider]` -- the PEP 518 location, and the one pyvider's own CLI reads -- so plating saw neither and fell back silently to the `[project]` name and to `[tool.plating] provider_name`. Also records the changelog entry, which the fix landed without.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
One fix, companion to pyvider 0.6.1.
Plating looked for
component_packagesand the provider name in the top-level[pyvider]table. Both shipped provider repositories put them in[tool.pyvider]— the PEP 518 location, and the one pyvider's own CLI reads — so plating saw neither and fell back silently to the[project]name and to[tool.plating] provider_name.component_packageswas effectively dead in both provider repos.[tool.pyvider]is checked first now, top-level[pyvider]after it,[tool.plating] provider_namelast. Eithernameorprovider_nameworks, matching pyvider's alias.The fix landed in #10 without a changelog entry; this records it.
Verified: 318 passed, 2 skipped.
uv buildproducesplating-0.6.1,twine checkpasses both artifacts.