Skip to content

Commit 5236025

Browse files
author
GitHub Actions
committed
Regenerated examples for 089b335
1 parent 089b335 commit 5236025

File tree

7 files changed

+9
-9
lines changed

7 files changed

+9
-9
lines changed

examples/calver_inc/.copier/package.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
# Changes here will be overwritten by Copier; NEVER EDIT MANUALLY
2-
_commit: v2024.21-15-g0e1088f
2+
_commit: b6f9f5e
33
_src_path: .
44
author_email: johndoe@example.com
55
author_name: John Doe

examples/calver_month/.copier/package.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
# Changes here will be overwritten by Copier; NEVER EDIT MANUALLY
2-
_commit: v2024.21-15-g388fbc2
2+
_commit: fd310ad
33
_src_path: .
44
author_email: johndoe@example.com
55
author_name: John Doe
6-
current_version: 2024.7.1
6+
current_version: 2024.8.1
77
django_versions:
88
- '4.2'
99
- '5.0'

examples/calver_month/RELEASING.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ When it comes time to cut a new release, follow these steps:
44

55
1. Create a new git branch off of `main` for the release.
66

7-
Prefer the convention `release-<version>`, where `<version>` is the next incremental version number (e.g. `release-v2024.7.1` for version 2024.7.1).
7+
Prefer the convention `release-<version>`, where `<version>` is the next incremental version number (e.g. `release-v2024.8.1` for version 2024.8.1).
88

99
```shell
1010
git checkout -b release-v<version>
@@ -58,7 +58,7 @@ When it comes time to cut a new release, follow these steps:
5858

5959
6. Draft a [new release](https://github.com/example_owner/calver-mminc1-project/releases/new) on GitHub.
6060

61-
Use the version number with a leading `v` as the tag name (e.g. `v2024.7.1`).
61+
Use the version number with a leading `v` as the tag name (e.g. `v2024.8.1`).
6262

6363
Allow GitHub to generate the release title and release notes, using the 'Generate release notes' button above the text box. If this is a final release coming from a tagged release (or multiple tagged releases), make sure to copy the release notes from the previous tagged release(s) to the new release notes (after the release notes already generated for this final release).
6464

examples/calver_month/pyproject.toml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,7 @@ Source = "https://github.com/example_owner/calver-mminc1-project"
7474
[tool.bumpver]
7575
commit = true
7676
commit_message = ":bookmark: bump version {old_version} -> {new_version}"
77-
current_version = "2024.7.1"
77+
current_version = "2024.8.1"
7878
push = false # set to false for CI
7979
tag = false
8080
version_pattern = "YYYY.MM.INC1"
Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,3 @@
11
from __future__ import annotations
22

3-
__version__ = "2024.7.1"
3+
__version__ = "2024.8.1"

examples/calver_month/tests/test_version.py

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,4 +4,4 @@
44

55

66
def test_version():
7-
assert __version__ == "2024.7.1"
7+
assert __version__ == "2024.8.1"

examples/default/.copier/package.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
# Changes here will be overwritten by Copier; NEVER EDIT MANUALLY
2-
_commit: v2024.21-15-g3337007
2+
_commit: 6e690cc
33
_src_path: .
44
author_email: johndoe@example.com
55
author_name: John Doe

0 commit comments

Comments
 (0)