Skip to content

Commit 9b540d0

Browse files
authored
bump version to 2.3.1 (#790)
1 parent 68453df commit 9b540d0

File tree

3 files changed

+15
-2
lines changed

3 files changed

+15
-2
lines changed

Cargo.lock

Lines changed: 1 addition & 1 deletion
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

Cargo.toml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
[package]
22
name = "pydantic-core"
3-
version = "2.3.0"
3+
version = "2.3.1"
44
edition = "2021"
55
license = "MIT"
66
homepage = "https://github.com/pydantic/pydantic-core"

README.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -98,3 +98,16 @@ If you want to contribute to pydantic-core, you'll want to use some other make c
9898
* `make lint` to run the linter
9999
* `make format` to format python and rust code
100100
* `make` to run `format build-dev lint test`
101+
102+
## Releasing
103+
104+
1. Bump package version locally. Do not just edit `Cargo.toml` on Github, you need both `Cargo.toml` and `Cargo.lock` to be updated.
105+
2. Make a PR for the version bump and merge it.
106+
3. Go to https://github.com/pydantic/pydantic-core/releases and click "Draft a new release"
107+
4. In the "Choose a tag" dropdown enter the new tag `v<the.new.version>` and select "Create new tag on publish" when the option appears.
108+
5. Enter the release title in the form "v<the.new.version> <YYYY-MM-DD>"
109+
6. Click Generate release notes button
110+
7. Click Publish release
111+
8. Go to https://github.com/pydantic/pydantic-core/actions and ensure that all build for release are done successfully.
112+
9. Go to https://pypi.org/project/pydantic-core/ and ensure that the latest release is published.
113+
10. Done 🎉

0 commit comments

Comments
 (0)