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.
This pull request introduces several updates to streamline the MultiSafepay Python SDK project, including renaming the project folder, updating workflow configurations, and enhancing project metadata. The most important changes are grouped into workflow adjustments, project metadata updates, and documentation improvements.
Workflow Adjustments:
multisafepay-pythontopython-sdkin the.github/workflows/code-quality.yamland.github/workflows/release.ymlfiles. This change affects paths for checkout, submodule setup, coverage reports, package publishing, and release asset uploads. [1] [2] [3] [4] [5] [6] [7] [8]Project Metadata Updates:
pyproject.tomlfile to align with modern Python packaging standards. Changes include specifyingpoetry-coreas the build backend, adding maintainers, refining metadata fields (e.g.,repository,homepage,license-files), and ensuring compatibility with Python 3.8–3.13. [1] [2]Documentation Improvements:
CHANGELOG.mdfile to document notable changes, including the initial release candidate (v1.0.0rc1) and dependency requirements. This follows the "Keep a Changelog" format and adheres to semantic versioning practices.