Skip to content

CMLDEV-1888: Migrate virl2-client metadata to PEP 621 - #270

Merged
tmikuska merged 2 commits into
devfrom
CMLDEV-1888-migrate-tool-poetry-metadata-to-pep-621
Nov 9, 2026
Merged

tmikuska merged 2 commits into
devfrom
CMLDEV-1888-migrate-tool-poetry-metadata-to-pep-621

Conversation

@marpauli-cisco

Copy link
Copy Markdown
Collaborator

Summary

  • Migrate virl2-client package metadata from legacy Poetry tables to PEP 621
  • Remove Poetry metadata deprecation warnings while preserving Poetry-specific development configuration
  • Keep existing resolved dependency versions unchanged

Changes

pyproject.toml

  • Move package metadata, runtime dependencies, URLs, and optional extras into [project] tables
  • Retain package exclusion, development dependencies, and export plugin configuration under [tool.poetry]
  • Remove deprecated license classifier in favor of SPDX Apache-2.0 metadata

poetry.lock

  • Regenerate lock metadata with Poetry 2.4.1
  • Normalize Python constraints and optional-extra package naming without refreshing dependencies

Verification

  • poetry check --lock --strict
  • poetry build --output <temporary directory>

@tmikuska
tmikuska changed the base branch from main to dev November 9, 2026 16:55
@tmikuska
tmikuska force-pushed the CMLDEV-1888-migrate-tool-poetry-metadata-to-pep-621 branch 2 times, most recently from b394046 to fae321b Compare November 9, 2026 16:56
@tmikuska
tmikuska force-pushed the CMLDEV-1888-migrate-tool-poetry-metadata-to-pep-621 branch from fae321b to c8c75b0 Compare November 9, 2026 17:00
@tmikuska
tmikuska merged commit 176ab66 into dev Nov 9, 2026
5 checks passed
@tmikuska
tmikuska deleted the CMLDEV-1888-migrate-tool-poetry-metadata-to-pep-621 branch November 9, 2026 17:08
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.

2 participants