This repository has been archived by the owner on Mar 8, 2024. It is now read-only.
Release 0.9 migration guide #98
Closed
EdgyEdgemond
announced in
Announcements
Replies: 2 comments 2 replies
-
See the README and CHANGELOG for more details on new features. |
Beta Was this translation helpful? Give feedback.
0 replies
-
@LachlanMarnham @myddrin latest release is here, should be fully backwards compatible with 0.8.x. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
With 0.9.x a few things have changed. The majority of features have been maintained for backwards compatibility.
This release brings with it some shiny new features:
pyproject.toml
-v
,-vvv
etcpost_process
support, including github issuesBreaking Changes
post_process
requiresheaders
to be defined in configuration.Migrating from 0.8
First step is to update the dependency pin, to maintain existing functionality using setup.cfg and bump2version (development is dead on this project). Update the pin to
0.9.0
and use the extras flagbump2version
All existing configuration should continue to work.
Migrating to pyproject.toml configuration
Run the command
changelog migrate
and copy the providedtoml
configuration into your pyproject.toml file, remove[changelog]
section from setup.cfg.When running
changelog generate
(replacing legacy commandchangelog-gen
. There may be some deprecation warning depending on your configuration, these can be silenced by following the suggestions in the warning.Migrating to bump-my-version
bump-my-version
is the new active fork of bumpversion and supports pyproject.toml configuration.To switch to this update the extras tag in your dependency from
bump2version
tobump-my-version
and update.For most configurations of bumpversion, it should be a simple conversion from setup.cfg
[bumpversion]
to pyproject.toml[tool.bumpversion]
, check out bump-my-version for details on any configuration issues that might pop up.At this point you should be able to finally drop setup.cfg completely.
Custom sections
If you are making use of custom sections, take a look at the
type_headers
configuration in the README, this replacessections
andsection_mappings
configuration.Beta Was this translation helpful? Give feedback.
All reactions